Bug #19356
closed
After some weeks with no problems a Typo3 website hangs up with a 'Cannot access protected property' error in the frontend
0%
Description
Hi there,
I upgraded a Typo3 websites from 4.1.7 to 4.2.1 and everything worked perfect. But after some time the first website hang up with the following error shown in the frontpage:
Fatal error: Cannot access protected property t3lib_pageSelect::$cache_getRootLine in /home/typo3_src-4.2.1/t3lib/class.t3lib_page.php on line 549
I tried to delete all caches (the typo3temp directory, the Typo3 cache and even cleaned up the database using menu 7 of the installation tool, but I couldn't solve the problem with this. I got another different but likewise error after deleting some caches:
Fatal error: Cannot access protected property t3lib_pageSelect::$cache_getPage in /home/typo3_src-4.2.1/t3lib/class.t3lib_page.php on line 192
The backend seems to work just fine, but the frontend just displays these errors (with error-reporting on in php.ini).
I decided to downgrad to Typo3 4.1.7 and this solved the problem - the page works again. But when I switch back to 4.2.1 the same error is displayed again. For that reason it seems to be a bug in Typo3 4.2.1 (?). Can somebody reproduce/confirm this error?
I am not sure, but may be the error was first triggered by a quota limit, so that no new file could be created - the quota of the website was nearly exceeded when i first saw this error. But when I increased the quota and cleared all caches the error was still there.
I found another user who seems to have the same problem posted in :
http://www.typo3.net/forum/list/list_post//80321/?page=1#pid302183
This is a german Typo3 forum.
(issue imported from #M9392)
Updated by Flummi about 16 years ago
Hello again,
as I found out, this problems seems to be caused by a special PHP optimizer that my hoster was running to increase performance. When we turned off this optimizer, the error disappeared.
It seems that Typo3 V4.2 has problems with this PHP optimizer where as previous versions of Typo3 worked fine with the optimizer.
Updated by Christian Kuhn about 16 years ago
The problem is related to your hoster and will not be fixed in TYPO3 (php or old/buggy php optimizer?)
If you still think this is a TYPO3 bug, please open a new issue with detailed informations about your server environment and a guide on how to reproduce. If you are curious you could help by nailing the first occurrence of the error message down to a specific subversion commit.