Hi,

Strange, it seems there are some characters submitted before session_start().
This could happen if you have characters (spaces or new lines) before tag ending tag in the three last one (under /model)

I could not find such.
Could you check on your local files ?
Maybe transfer could add extra "not expected" characters.

Hi, thank you for the quick reply!
I checked the files you suggested and can state the following:

• No extra characters are present before the <?php tag.
• No extra characters are present after the ?> in the mentioned 3 files.
• There's a carriage return character (^M) visible in Vi in some files. Could that be the issue, even though the character is not before or after the tags you mention?

If ^M is not after ?>, I don't think it is the origin of the issue.
But could you please tell me where you found them ? (files, lines, ...)

Also, how did you transfer files ? Unzip on local (windows) conputeut and ftp copy to target ?
Or direct unzip on target ?

Actually I see the ^M character in all php files (of course I didn't check them one by one, but the ones I checked do have it).
I downloaded the archive using the link on this website (link to SF) to my FreeBSD box and then unzipped the files to the directory where my webserver looks. After that I changed permissions on the files (to be owned by the webserver user).

Ok,
You did it the best way, so issue may not come from this side.

I just get an idea : could you just try and remuve ?> at the end of /model/User.php file
(I once met an issue with some PHP/Apache versions where closing tag in parameters.php file led to same kind of issue)

Just tried it. Doesn't work.
Shall I try to install a stable version and see if it works?

I tried to reconfigure the system and get the following error in the log file (version 5.0.1):

2015-07-09 14:45:59.999 ** ERROR ** Exception-[42000] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max k
ey length is 767 bytes
2015-07-09 14:46:00.000 ** ERROR **    For query : CREATE INDEX planningelementWbsSortable ON `pr_planningelement` (`wbsSortable`);
2015-07-09 14:46:00.000 ** ERROR **    Strack trace :
2015-07-09 14:46:00.000 ** ERROR **    #0 Sql->query called at [/usr/local/www/projeqtor/db/maintenanceFunctions.php:63]
2015-07-09 14:46:00.000 ** ERROR **    #1 runScript called at [/usr/local/www/projeqtor/db/maintenance.php:94]
2015-07-09 14:46:00.000 ** ERROR **    #2 include called at [/usr/local/www/projeqtor/tool/loginCheck.php:52]
2015-07-09 14:46:00.001 ===== TRACE =====
2015-07-09 14:46:00.001 ===== TRACE ===== Error # 1 => SQL error while executing maintenance query for version V0.6.0 (see above message)
2015-07-09 14:46:00.001 ===== TRACE =====
2015-07-09 14:46:00.001 ===== TRACE ===== *************************************************

Hi,

It is a non blocking issue but could lead to poor performance on planning display (an index has not been created).

To avoid the issue, you must configure MySql to with Innodb_large_prefix=true

Also, V5.0.2 has just been deployed.
Could you check if it fixes your first issue ?

Just tried it and it seems like the same error, but instead of line 125 it now gives error on line 2594:

2015-07-09 21:22:01.511 ===== TRACE ===== NEW CONNECTED USER 'admin'
2015-07-09 21:22:01.595 ** ERROR ** ERROR **
2015-07-09 21:22:01.596 ** ERROR ** on file '/usr/local/www/projeqtor/tool/projeqtor.php' at line (2594)
2015-07-09 21:22:01.596 ** ERROR ***** cause = getSessionUser(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "User" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition 

Problem solved:
I changed in php.ini from:

session.auto_start = 1

to

session.auto_start = 0

and managed to login. Topic can be closed as far as I'm concerned.

GReat you found the solution.
I will add a hack to :
- define session.auto_start Off in .htAccess
- check if session is automatically started and generate an explicit message.

Thanks for sharing the solution