[Typo3-dev] RC1 vs. RC2 strange behaviour

[Markus Waldinger]

Hi folks,

I'm using Typo3 on a Apache Server with PHP safe mode = on.

3.5:
Almost everything fine, but in the install tool he can't detect IM althoug I can execute IM with a written test.php. So safe mode shouldn't be the problem. (safe mode exec dir and so on is well configured)

3.6RC1:
Same as 3.5

3.6RC2: IM detection fine, everything seems to be ok. First time frontend view brings the "No pages are found ..." Message. First time backend view the following error messages Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php on line 689

Warning: Cannot modify header information - headers already sent by (output started at /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php:689) in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_userauth.php on line 236

Warning: Cannot modify header information - headers already sent by (output started at /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php:689) in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_userauth.php on line 237

Warning: Cannot modify header information - headers already sent by (output started at /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php:689) in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_userauth.php on line 238

Warning: Cannot modify header information - headers already sent by (output started at /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php:689) in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_userauth.php on line 239

Warning: Cannot modify header information - headers already sent by (output started at /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_db.php:689) in /var/www/web12/files/typo3_src-3.6.0RC2/t3lib/class.t3lib_userauth.php on line 240

And from then on I can see the error messages even in the frontend view.

Is there a way to force RC1 to detect IM? (Version 5.5.7 debian unstable)

Is it a bug in RC2?

Greets Markus