Upgrade Errors

Got Version 2.1.3-pl installed on my server. Tried upgrading it to 2.2.8-pl.

Upgrade was successful but when you look at the site this is what I see:

Fatal error: Call to a member function get() on a non-object in /.../html/core/model/modx/modrequest.class.php on line 192

PHP 5.2.17
MySQL 5.0.96
Linux/Apache

Tried rerunning setup numerous times and it tells me it was successful each time.

Didn't see much referring to that error that I was able to track.

I pulled the logs but this is all I see:

[2013-07-12 17:08:24] (ERROR @ /manager/index.php) Error 42S22 executing statement:
Array
(
[0] => 42S22
[1] => 1054
[2] => Unknown column 'modContext.rank' in 'field list'
)

[2013-07-12 17:08:24] (ERROR @ /manager/index.php) Could not prepare context: mgr

Any help would be greatly appreciated.

Tell us how you upgraded please? Did you FTP an unpacked 2.2.8 to the server or did you unpack the zip file on the server itself? If you used FTP, files could be missing or corrupted and you'll want to redo the upgrade with a fresh zip file extracted and merged with the existing files ON the server itself.

Additionally, did you log out and clear the core/cache folder's files prior to upgrading?

First step would be to clear the core/cache files, see if that helps.

Quote from: frogabog at Jul 12, 2013, 02:53 PM

Tell us how you upgraded please? Did you FTP an unpacked 2.2.8 to the server or did you unpack the zip file on the server itself? If you used FTP, files could be missing or corrupted and you'll want to redo the upgrade with a fresh zip file extracted and merged with the existing files ON the server itself.

Additionally, did you log out and clear the core/cache folder's files prior to upgrading?

First step would be to clear the core/cache files, see if that helps.

I followed the instructions here: http://rtfm.modx.com/display/revolution20/Upgrading+MODx

I downloaded the zip file, unpacked it locally, uploaded the files and merged the folder. Setup was successful but I get the error when I view the site.

I reuploaded the files this time I didn't merge and just replaced. Setup was successful but I get the error when I view the site.

I tried setup again this time I deleted the cached files all together so I could see anything written in the logs and that is what I posted above.

Not that you wrote it I realized I didn't clear the cache before I did the initial upgrade. I did make a backup though of the server and the database in case I need to upload all that again.

Hi,

I recently upgraded from 2.0.8 to 2.2.8 and also had some problems. The manager would allow me to login, but I could not access anything in the manager. I ended up turning the js and css compression off. Because I did not have access to the system settings through the manager, I needed to chase down the values in the database. But once I change the value to zero, the manager was up and running again.

Maybe give that a try?

It very well could be the js and css compression. But if setting both of those to 0 in the system_settings table doesn't work, do try extracting it on the server via file manager if you can, or use whatever extraction script the host provides rather than unpacking it locally. You never know...

GoDaddy seems to suck for many reasons. Ever think about jumping ship and letting the professional MODX hosting providers serve your needs?

Quote from: frogabog at Jul 12, 2013, 03:36 PM

It very well could be the js and css compression. But if setting both of those to 0 in the system_settings table doesn't work, do try extracting it on the server via file manager if you can, or use whatever extraction script the host provides rather than unpacking it locally. You never know...

GoDaddy seems to suck for many reasons. Ever think about jumping ship and letting the professional MODX hosting providers serve your needs?

I'll check into the system settings.

As for the modx cloud, I inherited this site and can't move it.

I didn't mean MODX Cloud, actually. See my signature below.

I've found, that when I tell the client the host is causing problems, my time is being wasted, and that I will have to charge them for the time it takes to solve the problem... They're happy to let me move the site to proper hosting and request a refund from the hosting provider for any pre-paid time.

This wasn't a server issue, the upgrade somehow goofed out and failed to update the database to the new definitions. That said, I do recommend SkyToaster as well

I managed to fix this for Eric by setting the settings_version system setting (in the modx_system_settings table) to the version he was upgrading from (2.1.3-pl) and re-running the setup. This tricks the setup script into thinking it still needs to run all the upgrade scripts (which updates the database) from 2.1.3-2.2.8.

I'm not sure how this managed to happen, but the error posted at the start of this thread is a red flag that the database is out of sync with what the files expect.. ie the database wasn't properly updated.