the law of averages » wpLicense

wpLicense Updated

Nathan Y. — Fri, 30 Dec 2005 21:58:05 +0000

So there’s a minor update available for wpLicense, and it’ll probably be most interesting to the Mac users in the audience. wpLicense 0.5.2 fixes a bug which broke the license selector under Safari. Oops. I’m not sure if the bug was Safari-specific or KHTML-specific, so if you’ve had problems with wpLicense under Konqueror, you may want to give this a try.

Using wpLicense

Nathan Y. — Mon, 22 Aug 2005 11:49:26 +0000

Ted is trying to use the wpLicense WordPress plugin and ran into some problems. So he wrote a little blog entry and when it showed up in my Trackback queue, I went to leave a comment, but can’t—you must be registered, and it appears registration is turned off (at least the link is, and I’m too lazy to try and find the URL). So here’s my reply; I’m dropping it here because classes start today, so I don’t know how long it’ll be before I get around to updating the actual documentation:

Hi Ted, thanks for trying the plugin. The most common reason the plugin doesn’t display the license icon and link has to do with themes. WordPress provides a “footer” hook which wpLicense uses, but in order for it to be called, your template must include a call to wp_footer();, probably in footer.php. The default theme, Kubrick, does that, so you might look at it’s footer.php for a sample.

I just looked at the documentation again, and that’s not clear, so I’ll try to get that updated. In the meantime, if you still have problems, feel free to email me directly (nathan at yergler dot net).

Thanks again,

Nathan

wpLicense Update

Nathan Y. — Thu, 21 Jul 2005 18:21:49 +0000

So about that “really, really works” comment—maybe only one “really” was in order. Anyway, wpLicense 0.5.1 is available. This corrects a bug which caused the selected license to mysteriously disappear when you edit other options. Very confusing, as you might imagine. So go, upgrade like the wind!

wpLicense Updated — And it really, really works

Nathan Y. — Tue, 12 Jul 2005 15:08:27 +0000

wpLicense 0.5 is out. The relatively large increase in version number (up 3/10ths as opposed to my usual 1/10th of a version) reflects the large number of changes as well as the amount of testing that went into this version.

In the bug-fix category:

Unbeknownst to me, my web host uses PHP 5 by default, so I happily used PHP 5-specific features such as SimpleXML without knowing it. Unfortunately, lots of people still use PHP 4, so some refactoring was in order. This release supports PHP 4 (> 4.3 for sure, possibly older although I won’t guarantee it).
I had also used libcurl in the previous version, which while it existed in PHP 4 wasn’t always turned on. We’re using a little more braindead way of calling the webservice now that should work with non-libcurl-enabled installations of PHP.

Finally, we fixed a rather annoying bug that caused Attribution licenses to be issues as 2.0, even though 2.5 is the current version. Feh.

This release also adds a new configuration option: “Include license badge in default footer”. If you use the default WordPress theme (or probably 90% of the other themes out there that call wpfooter(); ), checking this saves you the hassle of manually editting your template. The template functions are still available for manipulating and displaying the license information in other ways, this just seemed like a logical addition to make life easier.

All this combined with some (but not lots, mind you) UI-lovin’ means that anyone using an old version (yes, both of you) should go ahead and upgrade.

wpLicense Update Available

Nathan Y. — Mon, 20 Jun 2005 14:13:13 +0000

I’ve just uploaded the 0.2 update for wpLicense. wpLicense is a WordPress plugin which allows you to choose a Creative Commons license for your blog via a handful of functions which can be used in templates. The 0.2 release adds support for including Work metadata, as well as fixing a few issues with the AJAX rendering in the initial release.

I’ve also created a wiki page where you can record changes you’d like to see in the next release.