Manager non-functional after upgrade from 2.0.8 to 2.2.9

I have attempted to update a 2.0.8 installation (well, a copy of) to 2.2.9. I followed the general directions (updating all packages to the latest versions, flush cace, flush sessions & logout, trash the contents of the core/cache/ directory, etc.

It took a bit of experimenting to come up with a decent method of copying files from the upgrade directory into the installation directory. My first couple of failures appear to have been because of improper merging (e.g. replacing a directory and its contents with the upgrade directory), but I figured out how to use ZIP & UNZIP to solve this.

Now the upgrade appears to have worked, but when I log into the manager, it does not display properly and is unusable (see attachment). Before anyone asks, yes I did clear my browser's cache — multiple times. The site itself (i.e. front-end view) appears fine.

My browser is an up to date release of Firefox running under Linux Mint. The MODX site is hosted on a Linux server running Apache. When I use the Firefox "Error Console", there are pages and pages of dropped CSS declarations and 3 probably disasterous error messages at the end (I don't know how to save the console log and my attempts to take a screen snapshot failed). The 3 messages are identical and read:

TypeError: b[e] is not a constructor
http://testbed.teachbridge.com/manager/assets/ext3/ext-all.js

Does anyone know how to get this upgrade to work. I can restore the copy of the site (it is the one pointed at by "testbed.teachbridge.com". The live site is "teachbridge.com" and there is a test copy for the site developers.

Hi JRG,

I've heard of this happening when files get corrupted on upload. When you ran the upgrade, did you see any errors in your http log and/or modx log and/or php log? Do you see any errors in any of these logs when you run the manager?

Regards,
Tom

Quote from: stalemate at Sep 12, 2013, 10:43 PM

Hi JRG,

I've heard of this happening when files get corrupted on upload. When you ran the upgrade, did you see any errors in your http log and/or modx log and/or php log? Do you see any errors in any of these logs when you run the manager?

Regards,
Tom

Where do I find these logs? I looked through the web root for the hosting account (different domain) as well as the directory the test.teachbridge.com domain is pointed at. I looked for hidden files as well. I couldn't find anything.

I'll login to the hosting control panel and check if there is anything there about accessing "logs".
___

I uploaded the 2.2.9 zip file to the hosting server and unzipped it there by logging in with Secure Shell (ssh). I would have thought the unzip would have failed if the file were corrupted. The file size matched what I downloaded.

If you are on Unix, then try looking in /log (from the root) for http and PHP errors. MODX errors are in the manager in the Reports menu.

Quote from: stalemate at Sep 12, 2013, 11:07 PM

If you are on Unix, then try looking in /log (from the root) for http and PHP errors. MODX errors are in the manager in the Reports menu.

In the meanwhile, I'd logged into the hosting account and found an "error logs" icon. That led to a page that allowed me to "enable collection of error logs for 7 days", which I did. I then attempted to use the MODX manager and afterwards checked for logs in the directory that was referenced in their "help" — I found an error log that contained:

[Thu Sep 12 16:05:27 2013] [6837553] [fcgid:warn] (20014)Internal error: [client 94.153.11.136:64685] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function.

I seem to remember using SSH and trying to browse files outside the hosting account's root results in a permissions error. I'll take another look at / just as a double-check.

Great! Let me know how it goes.

Resolved thanks to information on Bob Ray's site.

Some hosting providers' setups muck up JavaScript compression. One needs to turn it off (by manually editing the MODX database using phpAdmin or whatever and changing the "compress_js" setting) and then delete core/cache/settings/*

Bob's site: http://bobsguides.com/modx-troubleshooting.html