The plugin toolkit has been getting a lot of useful classes recently, so I though a version bump was in order.
scbUtil is a collection of useful little functions that I was using in a lot of my plugins. My favourite is the debug() function. Then there’s html() and html_link() for HTML generation.
The more popular a plugin is, the more options it seems to have. This goes for themes too. Managing options is apparently brain-dead simple, using add_option() and friends.
However, when you find a plugin specifically wrote for cleaning up the Windows registry WordPress options table, you know it’s not all rainbows and unicorns.
Straight from the lab, we bring you the latest and greatest in front-end editing:
Currently, there is no easy way to change an image from your theme. You have to either override the image file through FTP or locate the code in your theme and modify it.
While frantically merging tags on a site using this plugin, I realised that it would be easier if you could use the checkboxes, instead of typing each tag by hand.
Now it’s possible.
Say you have two custom taxnomies defined: genre and artist. Currently, you can do the following types of queries on your site:
?genre=jazz
?genre=jazz&cat=1
But you can’t do this:
?genre=jazz&artist=Chet+Baker
Previous versions of this plugin allowed only a single type of archive, controlled entirely from the settings page.
Version 1.8 is a lot more developer friendly: any options set on the settings page can be overwritten.
One of the most longstanding complaints that WordPress gets is related to HTML formatting.
Over the last several weeks, there has been a steady stream of improvements going into Front-end Editor, largely as a result of your feedback. I’m happy to see people are using the plugin in interesting ways.
Since the launch of this plugin, several people have reported that autogrow wasn’t working properly in IE. After trying to fix the JS, I’ve came across a better jQuery plugin: Growfield.
This plugin ensures that a user will not see the same post twice.
It does this by keeping a list of single posts that the user has seen and then checking that list when redirecting.