Support Forum

Simple:Press 6 General Topics

Update from 5.5.5 to 5.5.6 problem

Update from 5.5.5 to 5.5.6 problem

Eric McMillan

Rookie

Free Members

Offline

Apr 25, 2015 - 3:09 pm

Hi guys,

Just moved my site to another host, and during the process I upgraded SP (on the new host) to 5.5.6.

However, the upgrade hung for around an hour with nothing going on except..

"
Upgrade is in progress - please wait"

BUT..also, it said..

"Upgrade Aborted
current build: 12610"

Which would appear to contradict what was said first.

Eventually after the hour or so I aborted it as it didn't appear be to be working.

So anyways the long and short of all this is that the forum simply doesn't work no matter what I do, if I re-import the old database from the old server (pre upgrade) plus copy over the old files it STILL doesn't work, and I get the White Screen of Death as long as Simple Press is turned on. Site works fine with SP turned off.

I'm at at total loss as to what's up.

Any help would be greatly appreciated.

Eric

Ike

Sawtry, UK

Member

Free Members

Offline

Apr 25, 2015 - 3:31 pm

Hey Eric,

This isn't too common but nearly always caused by a Javascript conflict. I'm guessing you have been able to upgrade fine in the past, have you installed any new WP plugins which you didn't have before? Might be worth disabling all WP plugins, and reverting to one of the default themes to see if that allows you to preform the upgrade.

Definitely the first and easiest thing to try anyway.

Yellow Swordfish

Glinton, England

SP Master

Offline

Apr 25, 2015 - 3:38 pm

That is the most likely. Another possibility though is if something is hijacking the AJAX call.

For example, there is a WP security plugin and also an http authentication app that both send data on any ALAX calls that are made. The problem with this is that the return data is not then what the SP upgrade script is expecting so it errors.

If you are getting the white screen however then that suggests a php error of some sort - and that should be in the php error log so it would be worth looking for a fatal error entry in there and reporting it back here.