WordPress 2.7 requires that plugins explicitly white list their options using a couple new functions. WordPress MU has required this security measure for a while, and it’s nice to see an evolved form of it brought to the core code. Migrating Plugins and Themes to 2.7 article in the codex offers some guidance, but here’s how it works:

First, register each option for your plugin during the admin_init action:

function myplugin_admin_init(){
	register_setting( 'my-options-group', 'my-option-name-1', 'absint' );
	register_setting( 'my-options-group', 'my-option-name-2', 'wp_filter_nohtml_kses' );
}
add_action( 'admin_init', 'myplugin_admin_init' );

In the example above, the value for my-option-name-1 will be filtered by absint before being saved to the options table. my-option-name-2 will be stripped of any HTML by wp_filter_nohtml_kses.

Then build a form like this prototype:

<form method="post" action="options.php">
 
<?php settings_fields('my-options-group'); ?>
 
<input name="my-option-name-1" id="my-option-name-1" type="checkbox" value="1" <?php checked('1', get_option('bsuite_insert_related')); ?> />
 
<input name="my-option-name-2" id="my-option-name-2" type="text" value="<?php format_to_edit( get_option( 'bsuite_insert_related' )) ?>" />
 
<input type="submit" name="Submit" value="<?php _e('Save Changes') ?>" class="button" />
 
</form>

Easy.

I actually use Event Calendar, which has been abandoned for some time. Looking at the alternatives listed in the Plugin Directory, Calendar, Events Calendar, and Gigs Calendar add full calendar management features to WordPress. While ICS Calendar, iCal Events, and Upcoming Events, simply offer the ability to display calendar data from elsewhere.

What I liked about the old Event Calendar plugin is how events were posts. Creating an event started with creating a new post. Searching and browsing events was the same as for posts. I haven’t yet tried any of the alternatives, but if none of them treat events as posts, I may find myself re-working the old plugin for better compatibility with current WordPress.

Ozh’s tutorial explains the details, but the short story is that we’ll soon get WP_CONTENT_URL and WP_CONTENT_DIR constants. And this is more than just convenience, 2.6 allows site admins to put those directories anywhere they want, so the constants will be the only reliable way of finding that info.

Lorelle and Samir both point to a number of plugins to do surveys within WordPress, but neither of them say any of them are that good. And Samir is pretty disapointed: “at the end of it all, I never did find my ideal online survey tool.”

Survey Fly is the best recommendation from both of Lorelle and Samir, but it isn’t WP2.5 compatible and was las updated in summer 2006. It’s also limited to tracking only one survey at a time. Ugh.

I announced the bSuite 4 public beta not long ago, now I’ve just posted a new version to SVN that addresses some of the bugs and fleshes out some of the features. I have yet to update the bSuite page, but here’s a preview of what’s new or changed:

• Additional stats reports
• WP2.5-style tag input tools on the Page edit screen*
• WP2.5-style category selector on the Page edit screen*
• WP2.5-style excerpt input on the Page edit screen*
• For multi-author sites: ability to grant edit permissions by role for each page (with a configurable default)
• An “include” shortcode that makes it easy to show content from one post or page on another.

About the new shortcode, use it like this:
[include post_id=“1234” url=“a url to a post or page in your blog” field=“post_excerpt”]

One of post_id or url is required; field is optional and defaults to post_excerpt first, then to post_content if there is no excerpt.

*Why would you want to input tags, set categories, or add an excerpt to a Page? They help readers find and explore our content. What’s so wrong with that?

I’ve had a lot of features on the table for bSuite for a while, but this recently discovered comment from John Pratt (whose Smorgasboard.net is a lot of fun), kicked me into gear to actually get working on it again. The result is bSuite 4, which is probably what bSuite 3 should have been all along.

The big news is that I’ve finally revamped stats tracking to work with caching mechanisms like WP Cache, WP Super Cache, Varnish, or whatever else. I’ve also got the search word highlighting working again, and that’s cache-friendly too. Yay for javascript, I say.

And in addition to making the stats cache-friendly, I’ve made them a little smarter, faster, and more useful. bSuite now tracks sessions, and reports both the number of page loads and the number of visitors to your site. To improve performance, stats are first recorded to a small table for incoming hits, then periodically processed (“migrated”) into the tables used to report stats. This reduces contention and improves write speeds for incoming stats hits.

The stats report now gets graphs for both the previous 24 hours and 30 days of activity. And because unlike external stats solutions, bSuite is integrated into your site, it can also report on your most popular tags and categories based on traffic.

I’ve also implemented a large number of improvements, bug fixes from the previous versions. Big thanks go to Matthew Batchelder (who helped with the javascript code), Jon Link (who both pointed out a lot of bugs in bSuite 3 and helped answer questions in the forums), Zach Tirrell (who helped develop migration strategy ages ago), and to everybody who’s posted a comment or review related to bSuite.

This is beta software, and some things definitely don’t work. The stats are working solidly, the other features appear free of catastrophic bugs, and I’ve had it running (in various stages of development) here at MaisonBisson for a month now. Still, read the warranty (there is none) and don’t blame me if Boba Fett jumps out of your server after installing it.

Get the details at the bSuite page, download bSuite 4beta1 here.

WP Contact Manager turns WordPress into a contact manager. It’s a combination of theme and plugins (including Custom Write Panel) that allows you to enter and manage contacts as blog posts (familiar, eh?). Use Members Only to secure access.

TDO Mini Forms “allows you to add highly customisable forms to your website that allows non-registered users and/or subscribers (also configurable) to submit posts. The posts are kept in ”draft“ until an admin can publish them (also configurable).”

I’m a big fan of the WP Geo plugin, but I want more.

My biggest complaint is that I want to insert coordinates using Google Maps or MultiMap URLs, rather than insert them in the modified story editor. So I wrote a bit of code that reads through the URLs in a post, finds the “maps.google” or “multimap.com” URLs, fishes the latitude and longitude out of them, and adds some geocoding tags to the body of the post.

Take a look at how it works with these posts in my archive…

You should see one or more blocks of links like the following (from my Osceola Weekend post):

geolocation: geo:lat=44.006336, geo:lon=-71.547260, geotagged, geolocation:44.006336,-71.547260 geobloggers

Go ahead and click the “geobloggers” link. I could have added these links using the old Geo plugin, but I still would have had to insert the coordinates separately. Actually, that brings up a good point: my code also inserts post metadata in the same format the Geo plugin uses, so I can take advantage of all the good functions it has, like the one that inserts the “<meta name=“ICBM” content=“44.006336, -71.547260” />” tag in the header of this post (caveat: I had to disable the add_action code in Geo that feeds the postmeta table, as it was conflicting my code).

I’m releasing this now, to start some public discussion, but please recognize that it’s a very early beta.

Download: bsuite_geocode.zip
Install: place unzipped “bsuite_geocode.php” file in your wp-content/plugins folder and activate it via the WP control panel. See the WordPress Codex for more detail.
Use: write posts as usual, adding links to Google Maps or MultiMap as appropriate. Links to those sites that have latitude and longitude components will be used to geocode the post.

Example of a working URL:

http://maps.google.com/maps?ll=19.355507,-155.072365&spn=.191780,.318003&t=k&hl=en

Example of a URL that won’t work (note how there’s no “ll=”):

http://maps.google.com/maps?q=decker+canyon+rd,+malibu+california&spn=0.019857,0.039750&hl=en

I’ve got a lot of features and uses in mind, so consider this only a start. Please post bugs and suggestions in the comments.

Also, see these previous posts on geolocating the news or geolocating everything or just search the archives to understand why I’m so excited about things like this.

tags: beta, blog, blogmap, blogmaps, blog gis, geo, geocoding, geolocation, geotagging, gis, google maps, lat, latitude and longitude, lon, map, maps, mapping, metadata, multimap, plugin, plugins, wordpress, wordpress plugin, wp plugin