Manager not displaying properly, notices & warnings on login

Hi,

I have just been tring to log in to the manager of a site I built a couple of years ago which I last edited about 6 months ago without a problem. Today when I log in I get the top menu bar across the top as it should be but the Revo dashboard welcome messages covering the rest of the window, no resources tree on the left etc. Above the dashboard are these messages:

Notice: Array to string conversion in /home/domainName/public_html/core/xpdo/xpdo.class.php on line 478

Notice: Array to string conversion in /home/domainName/public_html/core/xpdo/xpdo.class.php on line 478

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/domainName/public_html/core/xpdo/xpdo.class.php:478) in /home/domainName/public_html/core/model/modx/modx.class.php on line 1975

Warning: Cannot modify header information - headers already sent by (output started at /home/domainName/public_html/core/xpdo/xpdo.class.php:478) in /home/domainName/public_html/core/model/modx/modx.class.php on line 1985

I have run Bob Ray's excellent Sitecheck (from outside MODX) and get these two similar error notices:



I have looked at the server error logs and there are no errors.

Can anyone shed any light as to what the problem might be and how I might fix this?

Many thanks - Zaphodx

Server Info:
MySql 5.1.68
Apache 2.2.29
PHP 5.4.36
MODX 2.1.3

Client Info:
iMac OSX 10.9.5
Firefox 35.01
Safari 7.06

Hello,

You may want to try upgrading the site to a newer version of MODX, or reinstall the current version.

Hi AMDbuilder,

Yes, I thought that might be the way to go, that was the reason I was logging in in the first place but thought I'd check before trying to do the update. The problem I have now is I can't seem to log out or clear the site cache etc. so I'd have to do the update with a user still logged in which isn't good from what I understand.

From what I have read on here, the way to go would be 2.1.14 > 2.1.15 > 2.3.3. I'll wait for a bit and see if there's any more suggestions, but will go for it later.

Thanks - Zaphodx

I'm sure a few people will call me crazy, but I usually don't log out of MODX or clear the cache before performing upgrades. The more important aspect is making sure someone isn't actively editing the website when performing the upgrade - at least in my book.

You can always manually clear the cache by deleting the /core/cache, if that aspect concerns you. In regards to the actual upgrade it's generally suggested you upgrade to 2.2.15 and then 2.3.3, granted a direct upgrade to 2.3.3 should work as well. I've normally done direct upgrades or stopped at 2.2.15 if there are unsupported extras installed.

As always take a backup first so if anything does get messed up you can revert.