… and what we really need is for WPMU users to test it out. Please do not do this on a production site.
Ideally, have a test site you can play with (many MU people do) and just manually upgrade the WPMU install to the WordPress beta. Poke around, see if anything broke.
If you have read my in-beta codex instructions for enabling the Network, you do not need to do this if you are upgrading from a WPMU install. it will detect that the network is alreayd running, becasue the config files & htaccess already has lines in there.
You will notice some new terminology and the site admin menu has changed position. Blogs are now Sites, sites are now Networks, and the site admin has a cape. Er, I mean, is called a Super Admin.
The UI team has been working hard of late, and things are still moving around. For that reason (and a heavy workload of paying clients) I’ve been holding off on writing about all the changes – because there’s still some tweaks happening.
Awesome. We’ll definitely play around with it and provide some detailed feedback.
Right now we’re still fighting with MU stripping the tags from the pages of our main blog http://www.KendraToddgroup.com when the main blog is fully duplicated to a subdomain blog like test21.kendratoddgroup.com
It replaces them with br tags and so the font styles from the main blog no longer apply.
To complicate matters, the duplication is done via a plugin we wrote that duplicates Everything (except all the plugin settings) from the main blog, the idea being that this would make MU especially useful for corporate sites that want some control over the content of their agent/rep subdomain blogs.
Any advice on what to do about this problem would be much appreciated.
look at the unfiltered html plugin (on wordpress.org/extend).
Installed a fresh install and followed your directions for turning on the network. Worked like a charm. We run two seperate installs fo WordPress MU at my school. http://inside.isb.ac.th for teachers and http://blogs.isb.ac.th for students. Students are going to love the ability to create their own menus and change their background colors…..great upgrades.
I hoping we can still hack the kses.php file to allow things to be embedded. Students embed a lot of things off the web into their blogs so we need all those embeds to work. Voicethread.com being our #1 concern.
Hi,
i made a fresh installation of WP 3, activated MU and so far it seems to work. There’s one thing bothering me – if i want to use subdomains (not folders) for other blogs, i have to change my blog’s address from http://www.example.com to http://example.com. I’d like to revert it back. Any way to do it?
You can revert back to a single site by commenting out the following in your wp-config.php:
define('MULTISITE', true); define('VHOST', 'yes');VHOST may also be ‘no’.
Once you have done that, then you can remove the extra network tables from your database.
I wasn’t aware there was a restriction added to prevent using the www in a subdomain install.
I’m testing the multi-site aspect of 3.0 and have run into a weird quirk. When I create a new blog, it is given incorrect paths.
instead of: http://www.sitename.com/newblog
i get: http://www.sitename.comsitenamenewblog
There are no slashes. This happens for all the paths specified in the database (uploads, home, etc, )
Can I correct my primary site settings in mysql? Or is the culprit somewhere else?
Are multi-site blogs supposed to be grouped site under /sitename/ ??
Any advice greatly appreciated.
- matthew
Report the issue at WordPress trac: https://core.trac.wordpress.org/
p.s. I’ve manually corrected blog paths in mysql to confirm that everything else is working fine.
So far WP 3.0 is running smoothly for me as well. Where do we stand on using WPMU plugins? Will plugins like default blog settings continue to work in WP 3.0?
Most WordPress MU plugins should work in WordPress 3.0 without needing modifications. The plugin API didn’t change between 2.9.2 and 3.0.
Some will need to be tweaked. For example, SharDB needs a minor update in the next couple weeks.
“Blogs are now Sites, sites are now Networks, and the site admin has a cape. Er, I mean, is called a Super Admin.”
I *think* that you mean that the person who would now be called network admin has a cape. Under the new naming regime, there are also other admins, who may be capeless, and such people look after sites (which may be blogs).
I installed several fresh installs and followed your directions for turning on the network.
I did this several times on localhost and on a remote server.
Recently, when I put “define( ‘MULTISITE’, true );”, the following WordPress-Error appears: “No site defined on this host. If you are the owner of this site, please check Debugging WPMU for help.”
I removed and reinstalled all files and the directory for WordPress and I dropped an reinstalled the entire database.
I don’t get it: What goes wrong here?
The instructions don’t tell you to add
define(‘MULTISITE’, true);
Try following the directions on the codex page that Andrea linked to in the post.