As you may or may not know, WordPress has two simple helper functions built into it that make it easy to determine whether a checkbox/radio button should be checked or a select option should be selected.
Last week on the official Twitoaster blog, it was announced that the service would be shutting down almost immediately (as of March 20). Sadly, I have used the Twitoaster plugin on multiple WordPress installations because of its ease of use. It was great tool allowing WordPress posts to be pushed to Twitter automatically, and came with the added benefit of tracking when a blog post was tweeted (it even went as far as to allow you to automatically publish those tweets as comments on your posts).
When developing a new plugin for WordPress, sometimes you want to add a visual/WYSIWYG editor to one of your plugin’s settings fields. Unfortunately, most of the tutorials you’ll find online only explain part of what needs to be done in order to get that working. The main problem I have encountered when looking at these tutorials and example plugins is the fact that they only invoke the visual editor; they don’t offer any way for the user to use the editor in HTML mode.
When developing plugins for WordPress, most of the time I deal with semi-permanent settings with my plugins. A user goes to the “Settings” page for the plugin, they set things up the way they want them, and they expect those settings to remain that way until they decide to change them again.
However, there are times when you need to store temporary information that needs to either expire or be updated on a regular basis. There are functions within WordPress to help you with that, too. They are part of the “transient API” in WordPress. Basically, transient options are options that have an expiration date.
The way to handle this, quite simply, is to tell WordPress not to use its local copy of the library; but to use Google’s copy instead. To do so, you simply “deregister” the WordPress copy (for these examples, I will be showing how to use Google’s jQuery library), then register (and potentially enqueue) the Google copy.
The long-awaited WordPress 3.1 was officially released as the new stable version of WP sometime last night. This new version of WordPress brings with it quite a few major changes. It is highly recommended that you backup your entire WordPress installation (your files and your database) before performing the upgrade, as I suspect there will be quite a few plugins that won’t work the way you would expect with this new version (especially if you are a WordPress multi-site user).