Upgraded 2.2.6 to 2.3.3 on Ubuntu, now get blank page on manager

I've also heard that a corrupted table in the database can cause 500 server errors, so you might want to check the database tables.

And check the file/directory permissions; if your server requires, for example 755 and 644, if you have anything at 777 or 666 it can cause 500 errors.

I didn't until today as I've never needed it, but I added it prior to the 2.3.3 upgrade as the upgrade complained about it.

# JRW
date.timezone = "Europe/London"



Jim

I've enabled php error logging and error display, but I still get nothing. Does ModX disable error logging via php settings changes?

Try this: In the system_settings table (database), locate compress_css and compress_js. Set both to 0 if not already 0 (if already 0 (off), more installation/corrupted file hiccups need to be considered). Delete the files in the core/cache folder. Reload the manager.

Thanks Frogabog. Both are already zero. Clearing the cache and restarting doesn't help unfortunately.

I notice I have no logs folder in core/cache. Does that indicate a config error somewhere?

So frustrating to just get a silent fail with absolutely no diagnostics anywhere....

Progress!

I've added this to manager/index.php:

# JRW
$modx->setDebug(E_ALL);

and when I load manager I now get this:

Fatal error: Class 'GoogleAnalytics' not found in /var/www/thrislingtoncubicles.com/2013/core/components/analytics/elements/widget/widget.analytics.php on line 9

I've edited that component file to simply return an empty string, and NOW I can get into Manager, in a roundabout way. It doesn't look right, but at least it loads!

What's my best way to disable that component please?

Thanks again


Jim

I'm going nuts here. Having diabled the Analytics plug by simply returning '', I can login to manager and I can see the news feed and the security feed. I also see all the menus. But just about every menu gives me a black screen!

Crazy. Should I restore the 2.2.6 site and simply abandon ship?



Jim

Get into the database, and in the system_settings field change the compress_css and compress_js settings from 1 to 0.