Plugin Development

Will Norris‘ talk at WordCamp PDX introduces WordPress coding standards, common functions, and constants to would be plugin developers (and smacks those who’ve already done it wrong). Also notable: functions, classes, variables, and constants in the WordPress trunk.

Custom Installations

Just as WordPress has a number of hooks and filters that plugins can use to modify and extend behavior, it also has a cool way to customize the installation process.

Extending The WYSIWYG Editor

TinyMCE, the WYSIWYG editor in WordPress has a rich API to allow adding buttons and stuff, but the docs are hard to get into. We can get a jump on that by looking at how it’s implemented in other WP plugins. This code creates the buttons, while the function that responds to the button click and does the work is defined within the plugin. The TinyMCE plugins in core are also informative.

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.

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.

I’ve been following WP2.1 development, but Aaron Brazell’s post in the development blog wrapped up a lot of questions all at once.

The short story is that 2.1 is going to bring some really good changes that will allow more flexibility and better optimization of WPopac. Of the four changes Brazell names, the last two, the addition of the post_type column and a change in usage of the post_status column, are where the money is.

I’m awaiting the final release of 2.1 before building the necessary changes into WPopac, but the benefits will be worth it.

WordPress 2.1, WPopac, optimization, development

• memcached, a “highly effective caching daemon, …designed to decrease database load in dynamic web applications,” and the related PHP functions
• pspell PHP functions related to aspell and this pspell overview from Zend
• http_build_query, duh?
• current connected mysql threads * unix load average = system busy; reduce operations when $system_busy > $x

development, memcached, mysql, php, pspell

A: Because we compare them to the wrong things.

I’m in training today for a piece of software used in libraries. It’s the second of three days of training and things aren’t going well. Some stuff doesn’t work, some things don’t work the first (second, third…ninth) time, and other things just don’t make sense. At lunch, one of the other participants mentioned to the trainer that some of the activities in the software seemed to have too many steps, too many places to go wrong, too many turns between beginning and end.

The answer began by explaining that the most analogous activity would be the acquisition of books for the collection. Adding a book to the collection requires first identifying the book, reading the reviews, choosing to purchase, identifying a vendor and cost, identifying funding, ordering, receiving, cataloging…

The list went on, perhaps with too much detail, but it landed on the following: “there are at least 12 steps to just putting a book on the shelf. When you think about it like that, our software is easy.”

I bit my tongue at that moment, but I’ve been grinding my teeth about it since.

Here’s what’s eating me: You can compare one unlikable thing to any other unlikable thing and come out ahead, but what about “real-world” comparisons?

Paul Graham explains in his “Hardest Lessons For Startups To Learn” essay that developers often compare themselves to the wrong things, misunderstanding who their competition is:

A lot of startups worry “what if Google builds something like us?”

What you should fear, as a startup, is not the established players, but other startups you don’t know exist yet. They’re way more dangerous than Google because, like you, they’re cornered animals.

Looking just at existing competitors can give you a false sense of security. You should compete against what someone else could be doing, not just what you can see people doing. A corollary is that you shouldn’t relax just because you have no visible competitors yet. No matter what your idea, there’s someone else out there working on the same thing. (emphasis added)

Graham is talking to startups, but switch some words around and you’ll get my message: if you compare yourself to something that sucks, you’ll only be able to say you’re more or less sucky.

A better comparison for this product would have been against flickr, where activities that are closely analogous to those in the software we’re being trained on often require only one step. And taking Graham’s advice, the best way to approach it would be constantly ask “can we do this better?” “Could a competitor we don’t yet know about do this better?”

(Aside: social software is that which gets spammed, that which gets you laid, and that which you’ll need no training on.)

Please, stand with me now and repeat:

When something sucks I will say so. When vendors spout crap I will call them on it. My staff deserve good tools, my users need good tools, and I can’t afford to buy stuff that sucks.

Together, we’ll fix the world one product at a time.

bad answers, compare, comparison, competition, crap, developers, development, failure, future libraries, lib20, libraries, library 2.0, software, startups, suck, sucks, sucky, training, vendors