Support Forum

Page error after svn up 7975

CF Conrad_Farlow
Conrad_Farlow
Member

Hello I have the following error after upgrade:

Fatal error: Call to undefined function sp_find_css() in /problem-with-post-edit-buttonome/barbelfi/public_html/abftest.co.uk/wp-content/sp-resources/forum-plugins/admin-bar/library/sp-admin-bar-components.php on line 

This applies to all users. Any ideas?

4 Answers

New Answer

YS Yellow Swordfish
Yellow Swordfish
Member

You should really not be using svn now SP 5 is released as this is likely to be unstable. Where are you getting build 7975 from? We don’t have anything official with that build number?

CF Conrad_Farlow
Conrad_Farlow
Member

I just svn’d up from an ssh session and that is the number I get. I’ll download everything the old fashioned way tonight.

CF Conrad_Farlow
Conrad_Farlow
Member

Well that’s screwed things up well and truly. I downloaded the latest release and now get the following message.

‘It appears you are attempting to downgrade your Simple:Press Version. The Build or Version number in the sp-control.php file is lower than the currently installed version in the database.

You must restore your database to this earlier version before you can continue. You cannot simply downgrade Simple:Press files as the database has been upgraded beyond the version you are attempting to downgrade to and may cause irreparable damage to the database.’

I presume that the only way to fix this is to change the version number in the database to 7690 or did you actually make any structural changes at version 7975?

I upgraded my database after svn up as I usually do.

What can I do to recover this?

Conrad

MP Mr Papa
Mr Papa
Member

no, there were no db changes in trunk which is now the developmental version of 5.0.1…  go to sfoptions table and find the build option.. change the number back to 7960…  you should also edit the sp-control.php and change the version back to 5.0.0 and the build there to 7960… and you should be good to go…

trunk is our developmental version…  it is currently stable because there has not been any significant changes yet since 5.0.0 – certainly nothing that would cause the error originally…