That is, you can specify plugins that are automatically activated for all (or just some) blogs.

Check it out!

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

If you’re interested in playing with unfinished software, go check out the Hackadelic Multiblog Kit. Looking forward to v1.0!

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

A major improvement in this version is the way it handles defaults. Now you can set up defaults in the autoconfig file, and put just the differences into blog-specific config files. For example, if all your blogs use the same database, you can set the database info one time in mb-autoconfig.php, and then make blog-specific config files that only contain the table-prefix and nothing else.

If you are upgrading, from a previous version, please note the following instructions:

Upgrading

1) Upload the new multiblog folder to your wp-content directory. Copy wp-config.php and wp-config-vmb.php to the root WordPress directory. [Update: New versions of VMB no longer use the wp-config-vmb.php file. If you have it you can get rid of it; if you *don't* have it, don't worry about it. ]

2) The system no longer uses define() in the config files. Instead we are setting constants via an array called $vmb_const[]. For backwards compatibility, defines in blog-specific config files will still work for now (though it is deprecated). Any constants set in the autoconfig must use $vmb_const[].

3) Note that both mb-autoconfig.php and mb-config-{blog}.php will now be loaded (previously it was either/or). Anything set in autoconfig will be overridden by a matching pref in a blog-specific file.

That’s about it. Check out the readme and the FAQ if you’re having issues. Here’s the page again: Virtual Multiblog for WordPress.

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

If you’re having this problem and you’re using the $vusers[] list, try changing the order of the $vusers[] list. This alone may fix things.

I’ll try to get a “real” fix out soon (probably this weekend). A new version should be coming out anyway within days.

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

I’ve never been too active about showing this to people, because the function required to do it is not one I consider completely stable — I din’t want to show people how to do it only to have it break the next time I update the VMB system. In response to the requests, however, I am adding a function to the upcoming release (currently in private beta). You can have that ability right now, in a way that should not cause problems with later updates — just add a short function to your existing vmb-functions.php file.
(...)
Read the rest of Virtual Multiblog — how to use unique headers on blogs running the same theme (293 words)

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

Version 2.2 has a number of under the hood changes and bug fixes. It also includes an improved and clarified ReadMe, so if you’ve had problems, give it a look.

NOTE TO UPGRADERS: If you have used a previous version of Virtual Multiblog, be aware that the wp-config.php file has changed — you must replace the one in your main WordPress directory with the new version (included).

Also note — if any of you have been adventurous enough to use the functions in templates and such, there has been a change there as well. Where they were previously called as vmb::function(), they are now called through the $vmb object, like so: $vmb->function(). I’ve tried very hard to make this system “future proof”, and I apologize if this change messes anybody up. I do believe that the new setup is going to remain very stable going forward.

I put a LOT of time into this one, folks. There was actually a version 2.1.2 that I was going to release, but I kept rolling along with “Well, I should fix this too. And I wanted to add that thing. Oh, wait, what about….” And here we are.

You know, kind of like the just-released WordPress 2.4 2.5. (And yes, the timing relative to that was just a coincidence!)

Go get it!

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh