Aigaion bug tracker Syndication Feed

Several different characters are not converted correctly during migration from 1 to 2

2010-07-04T19:21:08Z

Bug ID:	157
Summary:	Several different characters are not converted correctly during migration from 1 to 2
Product/Component/Version:	Aigaion/2.1.2
Status:	Unconfirmed
Severity:	Moderate

When I migrated my customers Aigaion v1.3.4 to v2.1.2 several different special characters (German umlauts and different kind of quotes) were not converted correctly respectively are not displayed correctly in v2.

Some other users already reported similar problems.

Examples:

Title : Verk\"urzung
Journal: Gutachten f\"ur den Arbeitgeberverband
Reputation (Characters: 0xE2809E and 0xE2809C, italic double quotes)
Arbeit Analysen (0xE28093, long dash/minus)

Interestingly other attributes where converted without any problems:
Authors: Zentrum für Europäische
Also other umlauts in Title were converted u-uml is not good, a-uml and o-uml is good.

Please let me know when you need help in investigation.

Migration stops without error message. reason html code in publication abstract

2010-07-04T19:06:55Z

Bug ID:	156
Summary:	Migration stops without error message. reason html code in publication abstract
Product/Component/Version:	Aigaion/2.1.2
Status:	Unconfirmed
Severity:	Critical

When I wanted to migrate my customers Aigaion v1.3.4 to v2.1.2 it repeatedly stops without any error message (asking me where to safe the install.php (0 bytes in size) file).

Analysing the MySQL general query log pointed me to the problem in the following statement: INSERT INTO publication VALUES (...

The problem seems to be in the documents abstract attribute. Customer used a lot of html tags out of a Word MS Word document. This seems to confuse php/aigaion migration script. Probably the string is not properly escaped in aigaion?

When the abstracted was blanked out. The migration continued.

Problem can be reproduced at will. For further investigation I would be pleased to help. I have to ask customer first what kind of data I am allowed to provide.

Aigaion incompatible with PHP 5.3

2010-03-25T16:44:42Z

Bug ID:	155
Summary:	Aigaion incompatible with PHP 5.3
Product/Component/Version:	Aigaion/SVN
Status:	Unconfirmed
Severity:	Major

A number of errors appear on the screen, relating to the use of deprecated functions by both Aigaion and the included version of Codeigniter.

This bug can be solved by:
1. upgrading to the latest version of Codeigniter, and
2. replacing calls to deprecated functions with their equivalents. Most of the errors are related to the use of the deprecated POSIX regex functions; the replacement of these with calls to PCRE functions is straightforward.

A patch which should solve point 2 can be found at:
http://www.aigaion.nl/forum/index.php?topic=386.msg2169#msg2169

during bibtex export, capital letters should be put into {} to be understood as such by latex

2010-03-19T07:30:11Z

Bug ID:	154
Summary:	during bibtex export, capital letters should be put into {} to be understood as such by latex
Product/Component/Version:	Aigaion/2.1.2
Status:	Unconfirmed
Severity:	Trivial

if i'm not mistaken during bibtex export capital letters should be put into {} to be understood as such by latex.
this should not be too hard to implement by someone who knows the code.

Allow custom fields to specify URL display

2010-02-22T18:20:29Z

Bug ID:	153
Summary:	Allow custom fields to specify URL display
Product/Component/Version:	Aigaion/SVN
Status:	Unconfirmed
Severity:	Enhancement

I routinely add multiple URLs to my citations; the new custom-field behavior is a welcome improvement but the resulting entries are rendered as plain-text rather than URLs. Could fields be optionally labeled as "containing URLs" so that they render correctly?

Journals data management

2010-01-10T14:45:54Z

Bug ID:	152
Summary:	Journals data management
Product/Component/Version:	Aigaion/2.1.1
Status:	Unconfirmed
Severity:	Enhancement

What about a separate Journal table?

http://jabref.sourceforge.net/help/JournalAbbreviations.php

Feature: printing book tags to help archiving papery copies

2010-01-05T15:04:14Z

Bug ID:	138
Summary:	Feature: printing book tags to help archiving papery copies
Product/Component/Version:	Aigaion/2.1.1
Status:	Unconfirmed
Severity:	Enhancement

Would it be possible to add a feature that allow printing tags or labels (from pdf, for instance) to be attached on or inserted into the books/papers?

It would be a great help for those who are used to keep a papery copy of their bibliography or to put order in your library.

Error in RIS-import

2010-01-05T14:53:54Z

Bug ID:	146
Summary:	Error in RIS-import
Product/Component/Version:	Aigaion/SVN
Status:	Unconfirmed
Severity:	Moderate

When I import this RIS-record, catured from the Norwegian BIBSYS-library systen (www.bibsys.no), the second author end up as editor:

TY - BOOK
ID - 070551650
T1 - Tingsrett
A1 - Falkanger, Thor
A2 - Falkanger, Aage Thor
Y1 - 2007///
N1 - 1. utg. 1987 med tittel: Tingsrettslige arbeider
N2 - 5. utg. 2000
IS - 6. utg.
SP - 798 s.
CY - Oslo
PB - Universitetsforl.
SN - 978-82-15-01068-7
KW - Jus
KW - Tingsrett
KW - Eiendomsrett
KW - Eiendomsrett
KW - Tingsrett
KW - Jus
KW - Norge
KW - Tingsrett
KW - Norge
KW - Eiendomsrett
KW - tingsrett
KW - Norge
KW - eiendomsrett
KW - eigedomsrett
KW - sameie
KW - naborettsameier
KW - tomtefeste
KW - panterett
KW - sameige
KW - grannerett
KW - Noreg
ER -

Cookie path allows to steal sessions

2009-12-18T14:49:27Z

Bug ID:	151
Summary:	Cookie path allows to steal sessions
Product/Component/Version:	Aigaion/2.1.2
Status:	Unconfirmed
Severity:	Critical

After login to an Aigaion instance, a cookie with the session ID as well as cookies with login name and MD5-hashed password are set. They are set for the path "/".

This is a security hole in cases, where Aigaion is not reached via a dedicated domain, but is installed in a sub-path. Example: At the example university there is a server with user homepages, say, http://example.com. Every user gets a directory: http://example.com/alice/ for user Alice. If she installs Aigaion in her folder and logs in, Mallory can, with a simple CGI script at http://example.com/mallory/, also read her cookies.

In most academic environments this is not a major problem, but there are simple cases possible, where this can lead to a theft of the PHP session and to a security hole, exposing all data of the logged in user.

Fix: Every call to setcookie() *must* have the path part of AIGAION_ROOT_URL as third parameter. Also, in aigaionengine/config/config.php, $config['cookie_path'] must be set to the same value.

Caron's not converted correctly in BiBTeX export

2009-12-14T15:41:28Z

Bug ID:	136
Summary:	Caron's not converted correctly in BiBTeX export
Product/Component/Version:	Aigaion/2.1.2
Status:	Confirmed
Severity:	Trivial

If an author name contains a 'caron' it is not correctly transformed to valid LaTeX on BiBTeX export.
(this is correctly done for e.g. the 'cedilla').

Something like "Ž" should be converted on export to:
"\v{Z}"

I am not sure if all other special character conversions
are performed on exit, a complete table can be found here:
http://books.google.nl/books?id=PNTyn-ueEbYC&pg=PA79&lpg=PA79&dq=latex+accented+characters+caron&source=bl&ots=4D4BPtNR0S&sig=IH-diyskoRcZ3qaCHz-ZZ4pcPIg&hl=nl&ei=bY4aSs2VKZiq-Aaxi5Fr&sa=X&oi=book_result&ct=result&resnum=2"
(paragraph 5.4.7)