Wordpress MU 3.0.1 available but produces a error in upgrading

      .. download complete.
      Failed to extract source : Sub-directory wordpress-mu* was not found

.. failed! See the error message above for the reason why.

However upgrading to 3.0.1 needs some manual work.

First the file wp-content/blogs.php is obsolete and needs to be removed then you have to update the .htaccess to use the new wp-includes/ms-files.php file instead.

RewriteRule ^(./)?files/(.) wp-includes/ms-files.php?file=$2 [L]

Second the version 3.X has added a new define to wp-config.php

define( 'NONCE_SALT'

Which the admin will see that he needs to add when he/she visits the dashboard.

Personally there is no reason that the upgrade script needs to be used after 3.X as you can upgrade both wordpress and wordpress MU within the dashboard now. Unless you want to bug the admin to upgrade.

Closed (fixed)


I thought wordpress MU had been discontinued, and there was no release after 2.9.2 .. see http://mu.wordpress.org/

Apparently regular wordpress now includes the multi-site support. Also, you can't even select the 3.0.01 version of wordpress MU in virtualmin..

I edited the script installer to use 3.0.1 so thats why the installer tried... so since they merged MU into WP how are you going to merge all the users that install WP MU ?

Why have you not removed the WP MU installer since its been stopped?

I don't think there is any supported Wordpress MU -> regular wordpress upgrade path ... but you'd have to ask the wordpress folks about that.

I will probably remove or hide the wordpress MU installer eventually. Currently it is being kept around in case someone still wants to run the old wordpress MU..

Good idea .. I will disable the wordpress MU installer in the next release.

What are you going to do about users that used the old MU installer then ? Obviously they will not benefit from script update emails and it wont be maintained by VM anymore. Its script log will never work again. You going to delete all the script logs for MU as well ?

The change I've made is to just disable Wordpress MU from being installed - upgrades from older versions to the final one they released will still be supposed, as will managing or removing existing installs..

I'm not following..

I used the MU script and so did a few other clients. If you disable MU the only thing left is upgrade from within WP MU when it tells you to upgrade. That's fine fore the techy ppl but the dummies are only going to complain.

Wouldn't it be better to simply scan the scriptlog folder for name=wpmu and change that to name=wordpress using sed ?

What I did was change everyone that used wpmu and changed the script name to wordpress.

find /etc/webmin/virtual-server/scriptlog -type f -exec sed -i 's/name=wpmu/name=wordpress/' {} \;

and i changed wordpress long description to...

A semantic personal or multisite(formally called WP MU) publishing platform with a focus on aesthetics, web standards, and usability.

Does wordpress actually support upgrading from wpmu 2.9 to wordpress 3.0 though?

Your scriptlog change should work, as long as that kind of cross-grade is supported.

Well it should seeing that its wordpress that is downloading and upgrading for MU...

$ wget http://mu.wordpress.org/latest.zip
--2010-11-23 03:41:07--  http://mu.wordpress.org/latest.zip
Resolving mu.wordpress.org...,
Connecting to mu.wordpress.org||:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently

Location: http://wordpress.org/latest.zip [following]
--2010-11-23 03:41:07--  http://wordpress.org/latest.zip
Resolving wordpress.org...,
Connecting to wordpress.org||:80... connected.
HTTP request sent, awaiting response... 200 OK

And doing the upgrade inside the admin dashboard it also downloads WP to upgrade WPMU

So my changes work just fine. Test it yourself if you don't believe me.

Cool! Now I just have to figure out how to support upgrades from one script type to another in Virtualmin ..

Can you simply run a script when upgrading VM Pro and do something like my comment 10 ? I know you can run post scripts in rpm's and I am pretty sure you can do it with deb's.

Then simply adjust the description like I did for WP in comment 11.

Sure, a hack like that would work .. but I'd like to figure out a way to handle it more gracefully in the UI, so that the user can see that Wordpress MU is currently installed, but they can upgrade it to regular Wordpress.

So embed the upgrade in the old WP MU script. Instead of downloading you simply have the script run the find command and make the change. Or you can just used sed for that 1 site and change the script.

But you are still going to need to edit the WP script to show its the new Wordpress Multi-site also which you will have to add regardless of gracefully upgrading the old WP MU.

Ok, I figured out a good way to do this - in the next Virtualmin release you will be able to upgrade Wordpress MU installs to the regular Wordpress codebase.

So what was your solution ?

To allow WPMU to be upgraded, but using the regular wordpress .zip file.

Automatically closed -- issue fixed for 2 weeks with no activity.