Support Forum

Tried to upgrade to 5.05 and now it's stuck on maintanence mode!

21 Answers

New Answer

YS Yellow Swordfish
Yellow Swordfish
Member

The fatal error memory issue has occurred in a WP core file. This may be the catalyst for the other script errors the first few of which are again in WP core scripts although that last one appears to have something to do with credit cards – as it states  – so probably another plugin you have active.

I think you need to start with the memory issue – which may well be the cause for all your problems. Just because you do not have a history of such issues doesn’t mean you do not have them now. Many WP upgrades demand more memory than was needed before and every plugin you add will require more. There is no ‘standard’ as it really does depend on what you have actively loading.

I would suggest a good starting point would be to ask your host if they can increase your php memory to say, 128MB, even if only temporarily while you get things in order. If the problem still persists after that then it will be a matter of tracking down what is causing the remaining script errors – which might come down to a recently installed plugin perhaps.

BL Benny Lewis
Benny Lewis
Member

Update: in replacing the files via FTP, unlike the last time, this time my entire site went down with an error message (didn’t copy it; it was a call to a function that wasn’t there in one of the Simple Press files). My upload speed is not very fast, so I had to quickly delete the plugin to allow the site to work again, and am trying to use Vaultpress to restore the entire site to the state it was at a few hours ago.

It’s having a problem doing that, so there may be a database problem involved here. I’ll get back to you on how it goes, since I have to get in touch with Vaultpress to find out what the problem is so we can restore the backup.

BL Benny Lewis
Benny Lewis
Member

Just tried it again and still getting the “8148 – success” error, which stays there and leaves the forum in maintenance mode 🙁

I had left it a while because at least it was working in the previous version, but various other errors have built up on the site that look like they require an update to fix them (such as simplepress plugins perhaps not being compatible with the version I have), but updating is still not possible.

After updating, I have to revert back to a previous backup of the site (database and all files) for it to work again.

I’m on Dreamhost, dedicated hosting, and the most expensive option in terms of resources so I find it unlikely that it’s because my site’s resources are too weak to update. I’d appreciate any thoughts on this, since being stuck on the old version is becoming too impractical!

Thanks.

YS Yellow Swordfish
Yellow Swordfish
Member

Two questions: Firstly – did you ever address the potential memory issue? Next – when you retried this did you have Firebug open so you could check again for any return errors?

Looking at the upgrade script where it seems to be failing I can see nothing difficult or problematic that should cause it to fail. I really only have one suggestion which would be to place your site in maintenance mode and briefly switch to the Wp default theme and briefly deactivate a few of the WP plugins you are using and then try the upgrade again. This might well show us if this is just a php memory issue. If it goes through to the end then you can put everything back as it was. 

BL Benny Lewis
Benny Lewis
Member

Thank you!!! Finally, it’s all working 🙂

I don’t know what the problem is coming from, but by disabling ALL plugins and going to the default theme, and THEN applying the update, it worked without any hitches! (I had firebug monitoring the page just in case)

I reactivated everything and applied the current theme again and we’re in business. Thanks!! 🙂

It’s an extra couple of minutes work, but I may have to do this in future if I want to update. It may be more work than it’s worth to find out where the problem is coming from.

Thanks again!

YS Yellow Swordfish
Yellow Swordfish
Member

Probably one of two things. Either php memory or some sort of script conflict. But glad that trauma is over!