Host updated PHP from 5.1.6 to 5.2.14 - modx down, any suggestions?

--Post updated to reflect a later downgrade down to 5.2.14 from 5.3.3--

As the subject, my host has decided to update PHP on all servers to at least 5.2.x.

Here’s a sample of the worst error:

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »

PHP error debug
Error: Function split() is deprecated
Error type/ Nr.: - 8192
File: /var/www/vhosts/ihidmydomain.com/httpdocs/manager/includes/document.parser.class.inc.php
Line: 844
Line 844 source: $tempSnippetParams= split($splitter, $tempSnippetParams);

Parser timing
MySQL: 0.0058 s (1 Requests)
PHP: 0.1562 s
Total: 0.1620 s

This install is 0.9.6.1p2 and I can still log in to the manager. However, the public site is completely down.

Another site is running Evolution and doesn’t seem to want to let me log in, but most of the site is still displaying. Seems that any pages that utilise snippets are erroring the worst.

Has anyone got any ideas on how to fix this?

PHP 5.2.14
MySQL 5.1.50 (client, according to PHPinfo)
MySQL 4.1.22 (client, according to phpMyAdmin 2.8.2.4)
MySQL 4.1.22-log (server, according to phpMyAdmin)
pdo_mysql is enabled.

Thanks,

G.

0961p2 is ancient, and begging for a security compromise most likely. You really should upgrade to 1.0.4. it will get rid of the split function deprecation message as well.

Very true.. I only put off doing an upgrade when Evo came out because I was uncertain whether such an upgrade would break the "user area" (created using the code in this thread). I have a copy on a subdomain I can experiment with.

I’ve also got an Evo 1.0 install that’s been broken by this change but I’ll just go ahead and update that one, it’s not a client site at least.

Thanks for taking the time to reply Ryan, greatly appreciated.

Hmm.

Ok, I’ve upgraded a 0.9.6 installation to 1.0.4 as per the Wiki.

As far as I can tell, this has been successful but I’m still getting a PHP parse / session error instead of a website:


Asked the host about possible session config weirdness their end but they claim everything is fine.

Manager is still inaccessible: it seems to accept UN/PW but loops back and keeps asking for it; manually adding a new manager user to the database wasn’t successful as it doesn’t recognise the new UN when I try logging in.

I get the same session error (and manager loop) on another modx site that was previously running Evo 1.0 without issue.

The tips from this thread didn’t work unfortunately.

Going to refer my host to this article, see if that gets me anywhere. After that, I’ll be officially without a clue on how else to proceed.

Bit bummed that what had been a pretty solid modx-friendly host is now nothing but hassle. I’ve been considering switching to (mt), mainly to save some money as my current UK host is over £22/m, while (mt) is $20/m and seems to offer more..

Any other thoughts or suggestions?

It sounds like you just need to set a custom temp directory.

Try using this: http://tips-scripts.com/php_ini (read comments for how to change temp directory)

Also if you are based in the UK you may want to check out onesmarthost, you’re likely to get a much better response to MODx related questions, and the servers are local

I’ll second AMDbuilder about Onesmarthost.
Look at the Reseller plans, I’ve been a happy customer for a few years now.

Thanks for the host suggestions and tips! I’m actually US based now (previously in the UK), so the exchange rate makes most UK options less competitive. However, had some good news.

Turns out I can’t use php.ini, only .htaccess and that’s limited to certain things. That’s not the good news.

The host (JAB Web Solutions, UK based) changed the directory permissions and pretty much everything started working again.

Think it was due to FastCGI but at this point I’m simply relieved everything’s working again.

Thanks again! Now I can get back to making sites and stop stressing about stuff not working.