I am not sure from this if you are saying the upgrade process itself aborted – or if the upgrade concluded OK and this is what you are getting when you load the forum?

If the latter – can you go to the forum admin > Integration > Storage Locations and ensure (1) that they have the correct entries and (2) are both readable and writable…

Yellow Swordfish said
I am not sure from this if you are saying the upgrade process itself aborted – or if the upgrade concluded OK and this is what you are getting when you load the forum?

If the latter – can you go to the forum admin > Integration > Storage Locations and ensure (1) that they have the correct entries and (2) are both readable and writable…

Sorry, meant to say that the upgrade process itself aborts. The storage locations should be web-server writable.

The storage locations should be web-server writable.

Did you actually go to the page Andy suggested and see what SP thinks?

Mr Papa said

The storage locations should be web-server writable.

Did you actually go to the page Andy suggested and see what SP thinks?

Umm.. what page? The only option in Admin/Forum is “Perform Upgrade” … which fails.

If an upgrade needs to abort then there should be an abort message and a number. I did not see this in the notices you pasted here.
Is there chance that you could put your site into maintenance mode, switch to use the default WP theme and then try to run the upgrade again?

Yellow Swordfish said
If an upgrade needs to abort then there should be an abort message and a number. I did not see this in the notices you pasted here.
Is there chance that you could put your site into maintenance mode, switch to use the default WP theme and then try to run the upgrade again?

I copied according to the instructions on the upgrade page which are “Please copy the details below and include them on any support forum question you may have:” . The abort message and number (which where above..) were just:

Upgrade Aborted
6401

and after that the same text pasted in the first message.

I switched the theme to twentyeleven, but the result was exactly the same.

So it was looking in /site.com/ when it should have been /dev.site.com/ – so maybe that is the root cause of the problem.

This also confuses me: /site.com/wp-content/plugins/simple-press/sp-startup/site/sp-site-constants.php – where in earth is that ‘site’ coming from in the path which doesn’t even exist? And actually – in a couple of of the notices it does not read ‘site’ but ‘site.com’.

I am – to say thge least – somewhat confused here as aborting after 6401 suggests that no part of the upgrade actually took place yet you say the new storage locations were created.

One thing I can state is that yoiu would also need to change the entry in the sfoptions table where the option name is ‘sfpermalink’ as that will still be pointiung at the old domain name. So you could change that and try things again.

Yellow Swordfish said
So it was looking in /site.com/ when it should have been /dev.site.com/ – so maybe that is the root cause of the problem.

This also confuses me: /site.com/wp-content/plugins/simple-press/sp-startup/site/sp-site-constants.php – where in earth is that ‘site’ coming from in the path which doesn’t even exist? And actually – in a couple of of the notices it does not read ‘site’ but ‘site.com’.

I am – to say thge least – somewhat confused here as aborting after 6401 suggests that no part of the upgrade actually took place yet you say the new storage locations were created.

One thing I can state is that yoiu would also need to change the entry in the sfoptions table where the option name is ‘sfpermalink’ as that will still be pointiung at the old domain name. So you could change that and try things again.

(sorry for the delay, holidays in progress here)

Actually, the inconsistencies regarding “site” and “site.com” are just my mistake, sorry about those. I edited the output by hand (i do not want to reveal the URL’s on a semi-public forum). So you can assume that “site == site.com == dev.site.com” in the error log.

About the sfoptions table, i checked and that seems to be ok (sfpermalink == dev.site.com). Running the upgrade after that gives the same result still.

wp-content/ contains a sub-folder “sp-resources” with the contents:

forum-avatar-pool

forum-badges

forum-language

forum-smileys

forum-avatars

forum-custom-icons

forum-plugins

forum-themes

Any ideas what to try next?

i think the next step is to check for other plugins that may be causing scripting problems. You can do this by looking  at the MTML source code being generated. This codex article explians what to look for: http://codex.simple-press.com/codex/faq/troubleshooting/what-is-this-jquery-conflict/

Yellow Swordfish said
i think the next step is to check for other plugins that may be causing scripting problems. You can do this by looking  at the MTML source code being generated. This codex article explians what to look for: http://codex.simple-press.com/codex/faq/troubleshooting/what-is-this-jquery-conflict/

Ok, will do. Although there are only two plugins installed: Simple:Press and akismet. Also, don’t remember if i mentioned this but i tried using other themes (twentyten and twentyeleven) whilst running the upgrade but with the same result.

please let us know what you find… this one is quite odd and different…