Tagged tagline rotator

Tagline Rotator plugin v2.0 is now available

NB: If you are having any problems with taglines not rotating after the upgrade, please de-activate and re-activate the plugin. This is due to WordPress no longer calling the activation hook when you upgrade a plugin through the Dashboard.

As is often the case over the holidays, I had a little free time to update my Tagline Rotator plugin, which was in need of some serious cleaning up. Version 2.0 is now available on the WordPress plugin repository, and includes the following improvements:

  • Entire plugin is now class-based and the code is significantly cleaned up and better organized
  • All the MySQL queries that the plugin used are eliminated. Instead of using a separate table, the plugin now stores its data in the wp_options table
  • If you’re upgrading from a previous version, the plugin will pull your current taglines from the table and save them to the wp_options table. It will not delete the old table (something like wp_tagline_rotator), so your old taglines will still be there. Once you’ve confirmed the taglines are working properly, you can safely delete the table. I’ll be adding an option to delete any tables created by the plugin thru the admin dashboard in a future version.

As always, if you encounter any problems or have any suggestions, please leave a comment on the plugin’s homepage.

Tagline Rotator Plugin for WordPress version 1.1

Thanks to the holiday break, there’s a new version of Tagline Rotator available in time for the new year. You can read about it on the WordPress site here. The major improvement is that it now uses WordPress database prefixing. If you’re not familiar with this, it won’t affect your use of the plugin (you should still upgrade though). If you run a WPMU (multi-user) blog, or if you have several blogs sharing a single database, however, this is great news. It means you can run as many separate instances of Tagline Rotator as you want on the same database, and they will each use the prefix assigned to that blog. Please let me know if you run into any problems with this new version, and please use the automated upgrade feature of WordPress (or at least de-activate and re-activate the plugin when you upgrade). This will allow the plugin to rename its table using the WP prefix. Otherwise, you will get a mySQL error if your WP database prefix is not wp_ as the new version will be trying to access the taglines from the renamed database before it has been renamed. De-activating and re-activating the plugin fixes this error if you do get it.