Fatal error after upgrade to 1.0.2
Posted: Mon Oct 02, 2006 5:32 pm
Hi everybody,
just to say I think there's a bug somewhere with langage files in the core.
I've two CMS 1.0.2 sites -Still nice work, btw-, one installed from scratch and the problematic one upgraded from 0.13. Both have more or less same modules, and some of them are buggy when used with other langage than English (well, french in fact). I've noted two error messages to help developpers :
The error in modlang.inc.php is the most common (I've had the second one only two times or three) and happens when trying to view Albums in admin section or Calendar/events on frontend.
I've tried some tricks just for fun, like copy/paste en_US.php file, rename it fr_FR.php to implement in the Calendar drop-down langage list settings, still Fatal Error. And I tried the .htaccess super memory file trick (32M allowed !) but still the same.
It's not a real problem for me (I set the admin and frontend langage in English for the moment), but it's a bug.
Again, only for the upgraded one.
just to say I think there's a bug somewhere with langage files in the core.
I've two CMS 1.0.2 sites -Still nice work, btw-, one installed from scratch and the problematic one upgraded from 0.13. Both have more or less same modules, and some of them are buggy when used with other langage than English (well, french in fact). I've noted two error messages to help developpers :
Code: Select all
Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 45840 bytes) in ROOTPATH/lib/classes/module_support/modlang.inc.php on line 74
Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 801304 bytes) in ROOTPATH/lib/smarty/CMS_Compiler.class.php on line 36
I've tried some tricks just for fun, like copy/paste en_US.php file, rename it fr_FR.php to implement in the Calendar drop-down langage list settings, still Fatal Error. And I tried the .htaccess super memory file trick (32M allowed !) but still the same.
It's not a real problem for me (I set the admin and frontend langage in English for the moment), but it's a bug.
Again, only for the upgraded one.