anything in server error log?

or using firefox with firebug, see what is reported in the console? 

From the error log… (since cleaned up to shorten URL’s)

[02-Oct-2011 15:04:50] PHP Fatal error:  Call to undefined function  sp_get_system_status() in ../simple-press/sp-startup/sp-load-core.php on line 134
[02-Oct-2011 15:05:13] PHP Warning:  include_once(../simple-press/sp-startup/site/credentials/sp-rpx.php) [<a href=’function.include-once’>function.include-once</a>]: failed to open stream: No such file or directory in ../simple-press/sp-startup/sp-load-core.php on line 227
[02-Oct-2011 15:05:13] PHP Warning:  include_once() [<a href=’function.include’>function.include</a>]: Failed opening ‘../simple-press/sp-startup/site/credentials/sp-rpx.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in ../simple-press/sp-startup/sp-load-core.php on line 227
[02-Oct-2011 15:05:13] PHP Warning:  call_user_func_array() [<a href=’function.call-user-func-array’>function.call-user-func-array</a>]: First argument is expected to be a valid callback, ‘sp_rpx_process_token’ was given in ../wp-includes/plugin.php on line 486
[02-Oct-2011 15:05:19] PHP Warning:  include_once(../simple-press/sp-startup/site/credentials/sp-rpx.php) [<a href=’function.include-once’>function.include-once</a>]: failed to open stream: No such file or directory in ../simple-press/sp-startup/sp-load-core.php on line 227
[02-Oct-2011 15:05:19] PHP Warning:  include_once() [<a href=’function.include’>function.include</a>]: Failed opening ‘../simple-press/sp-startup/site/credentials/sp-rpx.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in ../simple-press/sp-startup/sp-load-core.php on line 227
[02-Oct-2011 15:05:20] PHP Warning:  call_user_func_array() [<a href=’function.call-user-func-array’>function.call-user-func-array</a>]: First argument is expected to be a valid callback, ‘sp_rpx_process_token’ was given in ../wp-includes/plugin.php on line 486

have to wonder if you have a corrupted file??  or permissions?

there are include file issues in the log…  and the first error in there is:

can call sp_get_system_status()

makes no sense… its in file sp-site-support-functions.php which is included about 4 lines before the call…

also, this error log might be bit of wild goose chase as to the upgrade because may not be related…

Please svn up again… just committed another change… having one hell of a time keeping sp 5.0 working with wp 3.2…  It really requires wp 3.3…  trying to limp through to the beta where 3.3. will be required…

Ok, everything is working.  I …

a) deleted the contents of my export folder

b) updated my SVN

c) exported again

d) deleted plugin folder on server

e) FTP’d updated export folder

All I can say is that the steps I went through that produced a broken update were the same steps I had gone through several times that worked without a hitch.  When I made my original post, I also tried on another test site in my network that has few if any plugins activated, and I got the same results, so I don’t think the error was due to any plugins on my main site.  Glad it is working again.

Out of curiosity, what does SP 5.0 require that is not in WP 3.2.1 but in WP 3.3?

wp changed how js is loaded… plus they changed the location of js folders and diff jquery ui packaged with wp is main… but some deprecated functions and other little stuff…

when we started building 5.0 we made conscious decision to target wp 3.3 because of release schedules but wp has slipped a bit which makes the sequence a bit precarious…

also 4.4.5 does not work with wp 3.3 either… so we are going to have to release a 4.5.0 when wp 3.3 ships… just for compatibility…

It’s a lot of work having fun

aint that the truth…

back in the 3.x days, we worked very hard to keep sp compatible with all wp versions… but just became too hard…  too many “if” statements on versions all over the place… makes dev and support harder…

so now, we only keep backward compat with older versions of wp if its trivial…  we can usually get 2 or 3 wp releases before we lose compat…

some of the wp 3.3 changes are pretty major – at least for us…  we probably have not been loading the js in the best method… 5.0 does but requires the better loading the wp 3.3 gives us…

Now you’ve got me worried. I need to get over to WP land and see what’s changing before I upgrade so I can prevent (hopefully) some breakage with the rest of my stuff.

I always run my master test site with wordpress trunk svn… always see whats coming…

and try to read the wp trac updates daily…