I accidentally upgraded all of my simple press stuff before I upgraded to wordpress 3.6
How can I roll back to simple press 5.2 and then get this upgrade to work… right now I keep getting an error when I try to perform the upgrade.
I accidentally upgraded all of my simple press stuff before I upgraded to wordpress 3.6
How can I roll back to simple press 5.2 and then get this upgrade to work… right now I keep getting an error when I try to perform the upgrade.
what error?
the only way to roll back to 5.2.6 is to restore the db backup you made before the upgrade (per wp and our recommendations)… db changes prevent you going back to old code…
@mrpapa Check out this screenshot:
https://www.dropbox.com/s/snmkjrnooeveslt/Screen%20Shot%202013-08-03%20at%206.14.47%20PM.png
If I deleted the forum and then reinstalled it, would I lose all of my members and content?
okay, confused… thought you updated sp first? no? have you updated wp yet (appears so)?
that error is the first script upgrade in the upgrade process… its attempting to alter a table to add a column… are you sure that your db user has alter table permissions? might need to ask your host… very standard/normal for it to, but some hosts get wonky…
Yes, I updated simple press first… unfortunately. Alter table permissions? I don’t see any reason why I wouldn’t have that permission, but I can check. This is an issue that I would bring to my OVC dedicated server folks? Would deleting simple press and reinstalling kill everything and remove all of my content or would that be a potential fix?
yes, uninstalling simple press would delete all your existing forum data…
yes, ask your server hosts… most hosts give it to users by default, but a handful do not… you want to ask them if your mysql db user has the alter table permissions… the upgrade script is trying to run an alter table mysql query and its failing…
and btw, I dont think it has anything to do with the sp or wp upgrade order… definitely not if alter table permission issue…
Ok… so I didn’t screw up majorly by upgrading out of order?
I guess that I just need to wait and see if I have that permission set up…. otherwise I don’t even know if a reinstall would work.
Is there any folder or series of folders that I can save via FTP and drop back into place to keep all of my forum data if a reinstall is necessary?
no… your forum data is all in the db… hence why you WordPress and us recommend making a db backup before upgrading… really for all plugins you should do this (but we all get lazy at times)…
so if you want your data, grab a db backup…
I assume you have tried the sp upgrade multiple times?
one more time with the browser console open and seeing the ajax response might provide more data too…
browser console? Give me some more info on that and I’ll do it right away!
I backed up my site yesterday, but I’ve done a lot of work on it since. I would love a rollback to be the last possible resort here.
If I do a database backup now and THEN delete simple press, would that have the same benefit or not at all?
what browser do you use? in FF is firebug… in IE is F12… chrome, etc all have the console you can open for inspecting html/css or looking at responses…
Lol…….
You’re going to love this:
{"status":"success","type":"upgrade","section":9884,"response":"Build upgrade section 9884 executing
. Status: success <br />","error":""}
<!--Cached using Nginx-Helper on 2013-08-03 22:47:26. It took 32 queries executed in 0.351 seconds.-->
<!--Visit http://wordpress.org/extend/plugins/nginx-helper/faq/ for more details-->
Disabled Nginx helper and proceeded without a problem in the world. Forum is back!
Thank you for your help!!!
good news! hey, hang around here long enough and you will learn lots of neat tricks!
I read before upgrading that the new Simple:Press was compatible with 3.5 but not tested for 3.6 so I did the same thing. Those notes were incorrect. It wasn’t a problem for me though after updating WP.
There should be no problems using 3.5 for the upgrade…
but where did you see that it was not tested for 3.6??? we explicitly said 3.6 was required and test through… in fact, after upgrading with 3.5, it would have warned it was not compatible…