Bug #53153
closed
Log Module throws fatal error (level of 100 reached)
0%
Description
On trying to call the Log backend on a TYPO3 CMS 6.2 beta 1, a fatal error is thrown:
Fatal error: Maximum function nesting level of '100' reached, aborting! in /path/to/core/typo3_src/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4201
Updated by Gone With the Wind about 11 years ago
This is actually a xdebug configuration problem. I have it installed, but there is no xdebug.max_nesting_level set, which has to be 250 (standard: 100).
The install tool actually shows that error, but only after the Log tool was called and has thrown the error in question.
Maybe this can be checked earlier already in the "System Enviroment" option of the install tool?
Updated by Ernesto Baschny about 11 years ago
- Status changed from New to Needs Feedback
Robert, thanks for reporting. But the Install Tool shows "PHP xdebug.max_nesting_level too low" warning in the Reports regardless if you have used the Log Module or not. Could you check it out again, please?
Updated by Gone With the Wind about 11 years ago
Yes, you're right! Sorry for this needless post!
I tried a new installation and there is a proper warning right at the beginning of the installation process!
Again, sorry for wasting your time!
best regards, Robert
Updated by Wouter Wolters about 11 years ago
- Status changed from Needs Feedback to Closed
Thanks for your answer and time to make TYPO3 CMS better:-)
Wouter