@trieth – had the same experience and reported bug to trac
http://core.trac.wordpress.org/ticket/15772
@mercime — thanks, and thanks for the heads-up on trac. I haven’t learnt my way around yet.
@trieth, you’re welcome. The auto upgrade failure didn’t happen when I upgraded other MU 2.9.2 installs to WP 3.0, thank goodness 🙂 so I was surprised with this issue on WP 3.0.3 upgrade from 2.9.2
Info on reporting bugs – http://codex.wordpress.org/Reporting_Bugs
Login to trac with username and password you use here at WP.org
Cheers.
@mercime — I have logged in to trac and asked for a cc: on your bug report. I’m guessing that’ll let me know when it gets fixed. It looks like a nice trouble-ticket system…
The auto upgrade from MU will *only* work to 3.0. and not above. As far as I know, devs were already aware of the issue.
Upgrade manually.
http://wpmututorials.com/how-to/upgrading-to-3-0/
It works to 3.0.1 as well, but I doubt anyone bothered to look into the me workaround for 3.0.2 and 3.0.3 … I suppose I could reopen the ticket we had to fix 3.0.1 and get the others patched as well but …
The problem is WPMU is looking for a zip with the name MU in it, and the new WordPress version ZIP does not have that. Go manually to 3.0 and then auto upgrade.
God, are we going to have to do this for every release until 3.1?
I sure as heck hope not. 3.1 was *supposed* to be the next release. this month even (which is probably not going to happen at this rate).
At some point though, the devs are gonna stop and say “tough”, you waited this long, do it manually.
anyone running wpmu from back that far should be familiar with manual upgrades anyway.
> anyone running wpmu from back that far should be familiar
> with manual upgrades anyway.
I have not been “running wpmu from back that far” and no, I’m not familiar with manual upgrades anyway.
The hosting company I’m using installs wpmu 2.9.2 with Softaculous, which I did YESTERDAY. I’ll open a ticket with them on the issue but it sure seems to me the simplest thing that could possibly work right now is supply the zipfile the auto-upgrader is looking for. I’m evidently not alone on this.
So the “right” thing to do at AN Hosting is:
0) Ignore the WPMU Softaculous installer — it is outdated (2.9.2) and
the upgrade functionality is broken
1) Use the WordPress Softaculous installer — this goes straight
to the current version
2) Follow the instructions here:
http://codex.wordpress.org/Create_A_Network
I would recommend never using any scripted install. The install itself can be done pretty quickly (the page says 5 minutes, which is only true of you have the SQL database made first 😉 ) and really the hardest part I’ve seen is sorting out HOW to make an SQL database, since every site is a little different.
Send a nastygram to an hosting about the WPMU thing, though. Cause damn.
The hosting company I’m using installs wpmu 2.9.2 with Softaculous, which I did YESTERDAY.
well then they are at least six MONTHS out of date, becasue as is stated elsewhere, WPMU is in development no more. that’s the very last version. If you like, you can send them to this thread. 😉
I am seriously not a fan of Scrpitalicious installs. not at all.
> If you like, you can send them to this thread. 😉
Did it. Thanks everyone.
At some point though, the devs are gonna stop and say “tough”, you waited this long, do it manually.
There will always be stragglers. I remember reading a thread here about someone upgrading from WPMU 1.1/1.2.1 just recently 🙂
@trieth – Good luck.
Yes, and we told them to do it manually 😉
