Tag Archives: WP Plugins

MobileAdmin Plugin 2.0 Update

Well, I finally got around to updating the documentation for users to create their own plugins in the WordPress MobileAdmin plugin. It’s designed to be very customizable and allow users to build and add extra support for their own devices via a simple plugin mechanism.

There’s still more that could be written (in terms of the documentation), but I go back and forth how much detail to get into, since for anyone who knows PHP well enough to read the code (and I think it’s pretty readable), it should be pretty obvious. I covered the high level stuff, and may or may not go through the details line by line later; right now, I’m leaning towards not doing that.

We also found out today that Oct. 22nd is the deadline date for the iPhone contest that we originally built this plugin for. The winning person or team will get free iPhones, courtesy of Matt Mullenweg. As far as I know, there is only one other team (3 people) working on an entry for this, and they haven’t released anything yet, but anything could happen in the next few weeks.

We’ve had our release out since Sept. 25th, and I think it’s a very solid contender for the win; I can’t think of much more that we could do better. Dan is working on polishing up the style even more, but other than that I don’t expect to have too many more changes before the deadline. Keep your fingers crossed.

WordPress Mobile Admin UI for iPhone

Dan and I just wrapped up a project we’ve been working on recently. It’s a WordPress plugin that adjusts the admin interface for WordPress to make it more useable on mobile devices like phones.

You can check it out at its home on the WordPress Extend site: Mobile Admin.

It’s specifically targeted for the iPhone, in somewhat of a response to the recent release of a similarly iPhone-targeted admin UI for Moveable Type, but the eventual goal is to support a common, slimmed down view of the interface for any mobile device, and then just add custom styles and behaviors (via script) only for devices that are known to support them.

The approach we took was to use a plugin to either hide, alter, or remove elements that interfered with the standard display, and then add a few things back in to tie it all together on the smaller size screens. Here are some of the more technical details:

  • CSS was the preferred method for changing things; the plugin will remove the normal CSS associated with the admin pages and replace it with one specific to the iPhone (and alternate stylesheets later, as more browsers are supported).
  • In some cases where CSS rules could not be used to extract things from the page, or items needed to be reordered, etc., we used PHP’s regular expression search and replace support to alter the output of the page just before it gets rendered to the browser.
  • Some items which were still necessary (a lot of the details on the post page, specifically) were left in but we added script to make the sections that contained the non-primary features collapsible, so as not to clutter the interface.
  • In one case (the manage posts page) the interface was table based, and while it was an appropriate choice for normal size screens, we needed to extract it from that grid-based format to make it “flow” better on the narrow screen. Again, regular expressions to the rescue.

We broke up the work by concentrating on what our areas of strength; I did most of the PHP and javascript coding, while Dan did most of the CSS styling. I don’t have much of an eye for design, even though I’m very familiar with CSS on a technical level. We’ve taken a similar approach on previous efforts, but this will be the first publicly released one.

You can read more details here on Dan’s post.

WordPress 2.2 Widget Plugins

Just a quick announcement / note that all of my currently supported widget plugins work “out of the box” with the widget system included in the latest WP release (2.2).

I still plan to go back and update the documentation a bit to reflect the new state of the WordPress world and the fact that widgets are now natively supported as well as catch up on some new feature requests, but until then, here is quick list:

I still haven’t decided on the tagboard one, but I’ll probably end up picking it back up if I can find the time.

Sidebar Widget Collapser Released

At long last, and after numerous requests, I’ve packaged up the plugin I wrote to add those collapse and expand links to my sidebar widgets.

The basic idea is that (if javascript is enabled) a script will run after the page loads that will go through your sidebar and add collapse and expand links to their titles, which will serve to show and hide any particular item. It will also remember their collapsed and expanded states for you via cookies.

The reason for doing it this way (as opposed to a server-side modification to the sidebar plugins) is that the collapse and expand links should not be added in the first place if the browser doesn’t support scripting, since their functionality is completely script dependent. Because this method uses javascript to modify the document and add the links, it will only add them when they would be able to function.

WordPress Theme Switcher Widget

As you can see, I’ve added a theme switcher widget to my side bar.

Now, if you don’t care for my default theme, you can pick a different one to view my site in.

This widget is a wrapper around Ryan’s Theme Switcher Plugin. Please see the plugin page for more info.

Part of the Peppermill

Well, only two days after downloading and installing Mint for the first time, I’m excited to announce that I published my Bird Feeder WordPress plugin to the Peppermill yesterday.

The Peppermill is a section on the Mint site for extra plugins (called “peppers” … get it? … “peppermint”), and so far, my entry is the first (and only) in its category. Here’s hoping for many more to come.

Feed hickup

If you read this site via an RSS aggregator, you may have noticed some items you had already marked as “read” showing back up again.

This should be a one time occurrence, since I just switched around my feed system to use a couple new plugins. One is the one I just wrote yesterday for integration with the Mint stats system, and the other is the FeedBurner plugin, which routes my feeds (regular posts and comments) through FeedBurner.

Hope it didn’t confuse anyone. I guess it’s more likely that this post itself will be confusing… oh, well.

Mint Bird Feeder - WordPress Plugin

I finally listened to Dan and installed Mint for site stats, and I was intrigued by the “pepper” (kind of like a plugin for the stat tracking system) called “Bird Feeder“, which shows you some stats about your feeds.

The only downside to this was that all the info I could find after a quick web search suggested modifying (or “hacking”) your core WordPress files to add the necessary include statements for the feed tracker to work.

This was no good, so I set out to develop a quick plugin to accomplish this task. Here is the result.

Thanks / props to Chris for providing a sample of the hard-coded solution (editing the wp feed files) which I used in creating the plugin to accomplish the same thing.

Plugin notice

All plugin downloads will be down for the moment, until I test and repackage them for WordPress 2.1, so if you’re trying to download one and it isn’t working, this is why.

UPDATE - All the links should be back up now. Everything should work fine in WordPress 2.1, except maybe the tagboard which I haven’t tested yet. I don’t think I really want to have it on my blog anymore, but I’m still planning to get around to rewriting it at some point, because it’s still pretty popular.

Links in Top Commenters

In case you hadn’t noticed, I updated my top commenters plugin to no include a link pulled from the “URL” field that was submitted with the comments.

The back story is that for a while now it was pulling a random URL, and the problem with that was for some people (specifically Dan) it was often getting an old URL. Initially, I thought about changing it to always get the URL from the most recent comment submitted by that person, but there were several issues with that approach, that I can go into in more detail if you’re wondering about them.

So, instead I decided to have the plugin check if there is a registered user with that name (by the “display name” property in their profile), and pull the URL in from their profile instead, which they can manage and change themselves at any time.

The one drawback to this approach is that most of the people (other than Dan, Nathan and Nate) haven’t registered. I could go in and create dummy accounts for those of you who don’t want to, and I probably eventually will (at least for those I have e-mail addresses for, so that you can reset your password later), but who knows when I’ll get around to that, so if you’re really itching to get your link back in that list, go ahead and register using the link in the sidebar below, or here.