I’ve just released Virtual Multiblog for WordPress version 2.5. This has some significant bug fixes and other improvements. If you’ve had trouble getting it to work in the past, I’ve reworked the code that determines which blog is active, and I think this will help a lot of people.
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 both wp-config.php and wp-config-vmb.php to the root WordPress directory.
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.
3 Comments
I’ve been using the previous versions of Virtual Multiblog with success but after updating to 2.5 I simply get an “Error establishing a database connection” error. None of the database information has changed. I use a separate database and config file for each domain. Tks, Darin
Darin — Look at my reply to Karrut, just above. You may have the same problem.
In VMB 2.5, the system reads both autoconfig and the specific configs, so if you set any CONSTANTS in autoconfig, it can cause problems.
I haven’t had a chance to update, but from looking at the release notes, I think this version does a good job in cleaning up the architecture of the VMB system. Good show!