Support Forum
If you are running the 5.0 Alpha, and your current build number is in the 9000s, you need to apply a manual change... you can see your build number by going to forum - toolbox - toolbox...
With the commit a few minutes ago, we have changed the build numbers and redistributed the upgrades... 5.0 had been using fictitious build numbers up in the 9000s since we didnt know where it was going to end up... As we get ready for upgrades delivered via the wp updater, nightly builds and getting close to beta, we needed to fix that up.
So now, if you want to get any sp updates to apply, you will need to manually change your build number... go to forum - toolbox - toolbox and change the build number to 6962 and be sure to check the button below for force upgrade.
From this point on, you should be good. If you dont update the build number, you wont know about any needed updates until we get into the 9000 range...
Thanks and sorry for the inconvenience...
Visit Cruise Talk Central and Mr Papa's World
should add you may need to set it to 6961 depending on your current version since the current build is 6962 and you cant set it to the same as current build… and do it after an svn upgrade...
if your build number is in 9000s you need this... if its already down in 6900s or in 7000s you should be good.
Visit Cruise Talk Central and Mr Papa's World
Not sure this is working for me. My build number was 9134 I think, changed it to 6962, checked the Force Upgrade To Build button and then Update Toolbox. Then when I went into the admin area I was prompted with:
Upgrade Simple:Press From Version 5.0.0 to 5.0.0 - (Build 6962 to Build 9134)
Checking the
Upgrade Aborted 9103 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 9104 success Please copy the details below and include them on any support forum question you may have: 8000 - success 8001 - success 8002 - success 9100 - success 9101 - success 9103 - success Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 Warning: Invalid argument supplied for foreach() in /problem-with-post-edit-buttonome/everythi/public_html/test/wp-content/plugins/simple-press/sp-startup/install/sp-upgrade-support.php on line 299 9104 - success
I did it again without checking the box and I get upgrade completed... but I'm back on build 9134 and none of my forums are available - they're in the admin area but I can't view them on the site.
Also tried it using build number 6961 and it's the same.
doesnt look like you did an svn update (as we said) before you changed the build #? Say this because it looks like the sp-control.php was still the version with build number of 9000+
so could be problematic at this point doing all those upgrades twice…
since its a test site, can you just blow away or reload the db from a backup (even if 4.4.5) and start over? AFTER an svn update… but if its working, maybe all is well... what is the build number now??? guessing back in the 9000s so you need to do an svn update and then change the build number to 6962 (or 6961)
everyone else: To be clear again, you need to do an SVN UPDATE on the sp core before you change the build number…
Visit Cruise Talk Central and Mr Papa's World
there is nothing to upgrade too...
we did some testing this afternoon on the simple press updates using the wp updater... so its possible you got really unlucky in your timing and check for updates during the 5 or 10 minutes we had an upgrade available... should be gone now...
but I will go check and make sure...
and most important, if you are running from SVN, do NOT attempt to update via the wp updater...
Visit Cruise Talk Central and Mr Papa's World
oh crap... lol... [Image Can Not Be Found]
we committed the changes after that for the build number change down to 6962... so yeah, the comparison is now checking against the now invalid 9000+ version...
sheesh, thanks for catching that for us... updating now...
may take a check or two for it to clear...
Visit Cruise Talk Central and Mr Papa's World
Mr Papa said:
oh crap… lol… [Image Can Not Be Found]
we committed the changes after that for the build number change down to 6962… so yeah, the comparison is now checking against the now invalid 9000+ version…
sheesh, thanks for catching that for us… updating now…
may take a check or two for it to clear…
Alright. Will check. As long as it's not only me 🙂
What's the new build number going to be?
per the first post in this topic, you need to svn up and manually change the build number to 6962 or 6961...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)