Another *nix coder/sysadmin » Widgets

WordPress 2.5 Compatibility

stormerider — Tue, 20 May 2008 15:37:16 +0000

I’m testing out some of my plugins on this blog, which is now running WP 2.5.1.

I see no need to continue development of the category or archives replacement widgets as the base widget code now has all the functionality that I added. Those two are now retired.

Morgan’s WIP Manager continues to function fine, as does Morgan’s Progress Meters and the Get Weather Widget.

Morgan’s Replacement Links Widget needs to be updated to work with the new way that 2.5 functions.

Morgan’s Replacement Links Widget 0.7

stormerider — Wed, 31 Oct 2007 06:16:46 +0000

This version requires WordPress 2.1 or above. Given that we’re on WordPress 2.3, and they’ve changed how links work since 2.1… it’s time for me to get my code up to snuff and out of the deprecated bin.

I also added in the ability to specify how you want to sort the display of links, per request.

Download here:

Morgan’s Replacement Links Widget version 0.7 (Option to control sort order of links.) — Requires WP2.1 or higher

Morgan’s Replacement Links Widget 0.6

stormerider — Sun, 28 Oct 2007 13:23:39 +0000

This is a minor feature-based version… Peter Lurie sent me a small diff to add support for the LanguageSwitcher plugin, which I’ve integrated. I’ve also added support to open links in a new window, per request.

Download here:

Morgan’s Replacement Links Widget version 0.6 (Option to open links in a new window, and support for LanguageSwitcher plugin.)

Morgan’s Replacement Links Widget 0.5

stormerider — Thu, 06 Sep 2007 20:59:11 +0000

Went to install this widget for a friend (Crystal Jordan), and we both noticed that when you’re using it in long form (not drop-down) and with multiple categories, it looks a bit odd showing “Links” and then the category title. I’m releasing 0.5 with the option to skip the header, for those folks who it would look cleaner without.

Download here:

Morgan’s Replacement Links Widget version 0.5 (Option to skip the header.)

Morgan’s Replacement Links Widget 0.4

stormerider — Mon, 07 May 2007 22:16:17 +0000

Went to use this widget while helping out The Novelty Girls, and I found a minor bug, so I’m releasing 0.4.

Download here:

Morgan’s Replacement Links Widget version 0.4 (Minor bugfix for multiple instance support when not using drop-downs and when limiting to specific categories.)

Morgan’s Replacement Links Widget 0.3

stormerider — Fri, 16 Feb 2007 18:14:35 +0000

Ok, I’m releasing 0.3 of this widget now, though I’m not 100% sure it’s quite right yet. Please take a look and see how it runs.

Download here:

Morgan’s Replacement Links Widget version 0.3 (Has support for multiple instances.)

Morgan’s Replacement Links Widget 0.2

stormerider — Sat, 10 Feb 2007 16:27:08 +0000

I’ve just put up 0.2 of the Links Widget. This is just a quick off-the-cuff version for WP 2.1. It needs work, but it’s a step in the right direction. Note that I’m starting to change all the file names (since I’m adding more options to the widgets than just drop-down select lists) so deactivate the old plugin.

With this widget, I want to support multiple instances of it and be able to specify via a drop-down list in the Widget control panel as to which category you want displayed within that instance of the widget. That way you can drag different link categories around on your sidebars easily…

Please give it a shot and see how it works for you.

Download here:

Morgan’s Replacement Links Widget version 0.2

State of the Hacker…

stormerider — Sat, 10 Feb 2007 13:16:00 +0000

WordPress 2.1 changed how the links were stored in the database so the drop-down links widget will not work with WP 2.1. I’ll be rolling a new version soon. Things have been pretty busy for me lately (see my LiveJournal for more information) but I’ll try to get this going as soon as possible. I’m really digging WP 2.1, so I’m looking to get all my widgets updated for it.

I’m also going to be branching out into developing some pure WP plugins, rather than just sticking to widgets. I’m going to take some of the writer’s tools I’ve developed for Evolution Writers and make them into WP plugins (like the WIP manager, the progress meters, etc.). They’ll support WP-MU as well, and I’ll be installing them over on my MU install at Authors Abode.

I’ve also been developing a LUA add-on for World of Warcraft called UFActionBars (Unit Frame Action Bars) which is basically a replacement for the defunct Group Buttons mod that died– along with a slew of so very many others– with the launch of 2.0.

I’m also working on StormChat again. Now that the server move has been completed I’ve moved the CVS repository over and started work on cleaning up the code (again). I’ve written a quick, off-the-cuff FAL to get it to work with WordPress for the wife and will be expanding it to work nicely with WP-MU so I can install it on Authors Abode as well.

I still haven’t had a chance to dig up documentation on how to localize widgets/plugins in WordPress. If any readers happen to have a bookmark they can toss me, that’d be much appreciated. Thanks!

New widget…

stormerider — Sun, 04 Jun 2006 08:42:16 +0000

Made a new widget: Drop-down Links Widget

I figured given the popularity of the Drop-down Archives Widget, that a drop-down version of the links list was probably in order. I don’t know about you, but I have a lot of different feeds that I watch (via a Gregarius installation).

I’ve added the sanity check of silently failing if the AWP is not activated to this from the beginning.

Widget Updates…

stormerider — Sun, 04 Jun 2006 05:34:38 +0000

I’ve rolled new versions of the widgets with a minor bugfix. If you activate a widget without having the AutoMattic Widgets Plugin (AWP) turned on, you’ll either get a blank page on your site or you’ll get an error (most likely “Fatal error: Call to undefined function register_sidebar_widget()“).

The new versions will silently bypass the widget registration process if the AWP is not activated. It’s not exactly the way I wanted to do it, as I would have preferred to deactivate the widget automatically if the AWP wasn’t activated. The problem is, given how plugins are loaded, my widgets are often loaded before AWP, so they would never be active.

New versions: