Support Forum
Support Forum
Offline
I have a site running 5.0 alpha (grabbed from SVN, the very last update before you went beta).
Now that WP 3.3 is out, what's the proper upgrade path to 5.0 beta?
Should I...
1) just use the automatic updater? (I'm guessing no...)
2) download the beta, deactivate the alpha, delete the alpha, upload the beta (my guess)
or something else?
Is the 5.0 beta download the full package, with alll updated themes & plugins?
Btw, Google XML Sitemaps is broken under WP 3.3. I guess I have to move up on the priority list doing that WordPress SEO compatibility plugin.
Offline
You should see in the wp updater that there is a newer version available and should be able to use that.
The core, plugins and themes will all update individually. The normal download packages from our site are arranged the same way.
The sitemaps plugin is broken? No - I didn't know. Where did you discover this please?
 |
YELLOW
SWORDFISH
|
Offline
Ok, I'll try the WP updater.
On sitemaps, see this WP thread. You will see numerous reports on the WP forum. I reported it to Ipstenu the other night on Twitter. My specific report was that beta 7 of the plugin is broken under multisite. I also tested all of the other betas under multisite and they are broken too. The "development" version is actually older than the betas; it's just the current stable release. That current stable release can't be activated on multisite so I haven't gotten around to testing it.
The error isn't obvious. You have to look at your sitemap.xml, and you'll see the error at the top of the URL. If you check in Google Webmaster Tools, you'll see that the sitemap wasn't read. If you look at the debug link on the sitemap plugin, you'll see (at least in beta 7) in 1 place that it was expecting a string but got an array. I can't say this broke it, because I never had reason to look at the debug data before now.
I also didn't check the current stable release on a stand-alone WP 3.3 installation. The repository says it works, but I'm not sure if that is accurate in light of the fact that the error isn't obvious.
If you have a fix, many will consider you a hero.
Offline
it "seems" to be working for standard wp installs... but thats only a cursory glance - dont notice any errors in sitemap and no issues at google webmasters for multiple site...
Visit Cruise Talk Central and Mr Papa's World
Offline
I checked, and for single site installs with version 3.2.6 (the latest stable release), it does seem to work.
But none of the betas work on multisite. The stable release will activate on multisite, but it says it does nothing. The betas produce different errors. Beta 7 does this:
Warning: Invalid argument supplied for foreach() in ../wp-includes/query.php on line 2746
That's when attempting to view the sitemap.xml. Did you have different results on multisite? Using which beta?
Offline
when I said multiple site (sic), I mean on multiple different sites running sp and google xml sitemaps... not wp multisite... I dont have any live or test sites running the two together...
Visit Cruise Talk Central and Mr Papa's World
Offline
Updating from within WP 3.3 didn't work. It said my installation was up to date, even though it is clearly not, since it is just the alpha version. Off to grab the download.
Offline
odd. the update has been tweaked/improved a bit during later part of alpha and in beta... but has been working for alpha (and beta) folks unless you were a bit out of date...
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)