Open ReSpawN opened 10 years ago
ReSpawN submitted:
In addition, while these errors are generated out of the errorlog.php, I've traced the error further back to modsessionhandler.class.php, perhaps a good starting point for debugging.
ReSpawN submitted:
Update...
I've read a couple of posts concerning this problem, but almost all didn't seem to work. Clearing the cache, reuploading core files -- nothing did the trick... until I disabled APC in the php.ini. Not really a decent solution if you ask me, but it works -- for now.
Idea's came from this post: http://forums.modx.com/thread/75601/catchable-fatal-error-xpdoobject-load#dis-post-418871
;extension=apc.so Dat epix fiks.
Thank god for our FGCI PHP per-user php.ini.
ReSpawN created Redmine issue ID 10369
I've got the following start up error:
It happens somewhere along the first loads of MODX, somewhere within the loading of the user or the retrieval of the session. These 3 queries are executed before this error occurs. Yes, while this is a recoverable error, modX is undefined within the log function, thus it's can't recover from the error. modX::LOG_LEVEL_ERROR isn't defined yet, (as the error occurs in the __construct of modX), but xPDO is, however, errors aren't logged via xPDO.
Note: This is perfectly debuggable.
Create a Plugin
Enter the code as it's snippet content:
Only fire it "OnWebPageInit"
Refresh the front-end of MODX
Tadaa, error.
These 3 queries are performed in boot-up.