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

I finally figured out SVN, so it’s on the official WordPress repository. In layman’s terms that means that automatic update will do the job for you (look at the Plugins page in Admin).

Here’s the link. Check it out for details. Mainly bugfixes since 1.1, but a few other changes in the mix as well….

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

Now it has an option to toggle logging to the PHP Log, or a table in the database, or both. If logging to the database you can view the records on the admin page (under Plugins->Deprecated Calls. It also has a test function, and if you’re using WordPress 2.7 or up, it will even clean up after itself if you delete it.

Again, this is primarily of use to those who write plugins and themes.

Here’s the link.

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

• Fully WP 2.6 compatible
• Lots of code cleanup
• Fixed spotlight image so it’s NOT inside the first paragraph
• Spotlighted comments add “clear: both” div to end so spot images don’t extend past comment bottom
• Moved Settings screen to Settings menu (was in Comments menu)
• Added direct link to Settings from Plugins “Action” column
• Added Settings page footer
• Moved all functions into a PHP class
• Added get_options and localization functions
• Added nonces to Settings page — better security

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

The biggest change from the user end is that localizations (i.e. translations) now work. (The had worked previously, but broke somewhere along the way.) It includes French and Italian translations.

If anyone out there would like to translate the plugin for others who speak that language, see the readme in the “languages” folder, and send it along to me – I’ll include it in the next version.

Actually, the French and Italian files could probably use some updating too.

Go get it!

Full changelog (for the geeks):
* Fixed design flaw introduced in 2.1.1. Style option now stores file basename relative to styles directory -- should not store full URL if we're going to let user change the directory.
* BUGFIX: Localizations not working. (Incorrect path)
* Localizations (.mo files) will work directly from languages/ folder
* Changed init() to class constructor -- no more hooking "init" action
* Moved activation hook call to constructor
* Minor code cleanup to comply with WP Coding Standards

http://codex.wordpress.org/WordPress_Coding_Standards

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

• Increased efficiency of version checking
• Fixed a small bug with the admin footer
• Significant cleanup of Style selection code
• Moved Default style to resources folder so it can’t be misplaced
• Significant error checking RE missing or renamed styles
  • If chosen style is missing, falls back to default rather than linking nonexistent file

Two notes if you’re upgrading from an old version:

1. You may discover that the Styles dropdown in the Settings screen now has two items called “Default”. If so, go into /jspullquotes/styles/ and delete Default.css — you don’t need it anymore.
2. There has been a change to the way the Style setting is saved. It should auto-update existing settings, but if it doesn’t work you may find that your chosen style has reverted to the default. If so, simply go into settings and re-save with the style you want.

As of 2.1, JavaScript Pull-Quotes is fully compatible with WordPress 2.6.

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

So, if you’ve been having trouble getting the latest version to work, try version 2.4. It’ll make you smile.

One more thing — before you upgrade to 2.4, deactivate the Virtual Multiblog Support plugin. In fact, you can delete the thing — it is no longer needed. The system now calls that functionality automatically without the kludge of a separate plugin to hook in to.

One more one more thing — I still haven’t finished testing with WordPress 2.6, but I believe that as long as you don’t relocate wp-config.php or wp-content, it should work without problems.

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