My take on this is quite simple: From the user perspective, plugins should be invisible. That is, the fact that such-and-such part of the interface was made by a plugin should be invisible. The best design for a plugin is to seamlessly blend into the existing interface so that someone who didn’t already know would not realize that that thing there is not part of the basic system.

Therefore, if you have a plugin that has something to do with managing plugins, go ahead and put the screen under the Plugins menu. If it just has a basic settings screen, put it under Settings. If the screen lets the user manage something, then “Manage” is probably the right place.

I have a plugin that lets people easily put pull-quotes into a post. The admin screen for that plugin allows people to set options that control what the pull-quotes look like. Therefore I put the screen under “Design” (“Themes” in WP < 2.5) because it's primary function was to control the appearance of part of the blog. The Design menu is where it made the most sense.

So: Don’t make your plugin scream “this is a plugin” to the end user. If it were going to be part of core WordPress, what menu would you expect the screen to be under? Put it there.

(On a related note, the header on the top of your plugin’s page should not say “Such and Such Plugin” — it should just say “Such and Such”. I’ve seen some otherwise wonderful plugins made so that the header on the admin page is the file name. Yuck!)

Coming up next: How to put a direct link to your plugin’s admin screen on the Manage Plugins page.

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh

Case and point. I got a call from another office because somebody’s printer is not working. I travel to that office, and ultimately just delete and reinstall the printer. Open up Word, insert some test garbage, and print. Done.

I come to work the next day and have a call in that the printer is not working. Turns out that it is not working for some particular program that (unbeknownst to me) needs a particular batch file/hack to run when Windows boots so that it can print. (Didn’t need the hack when we were on Windows 98.) Oh, yeah, I made a small change to the printer name when I reinstalled it. We just need to change the printer name in the one-line batch file…

…which requires me to travel to that office again. Unless I can do it via remote. Windows XP has this thing called “Remote Assistance”. I can have the person on that computer send me a request, and I can then just click on a link and run her computer remotely and fix the file. Neat, huh?

Nope. The program works by sending the request file via email, and she gets an error saying that Outlook Express is not set up. She doesn’t use Outlook Express, she uses Outlook. I instruct her to go to Control Panel and change the default email program to Microsoft Outlook. She does so and tries the request again. Same error. I send her back to Control Panel, and the default has reverted to Outlook Express. What the Hell???

Some Google searching turns up the little tidbit that you cannot change your default email program unless you are an administrator, as it is a system-wide setting. Huh? So apparently in Windows XP, two different users with two different accounts on one computer can’t use different email programs? What kind of drunken half-wit prick thought that was a good idea? (I’m looking at you, Bill.) Naturally, Windows does allow you to change the setting, but then silently reverts it the moment your back is turned (i.e. you close the settings window). This is one of the worst kinds of software failures — when a program changes things silently. Microsoft programs do this all the time — I think it must be in the style manual:

Help the user by constantly making assumptions about what they really meant to do, and then silently change what they actually did to what the software assumes they meant. Remember, people are stupid and software is smart.

I realize that the remote request likely won’t work anyway because I’ll be remote-controlling a non-admin login. Huh.

I call the person at that office who has admin access. He’s not a techie, but I should be able to talk him through it. I don’t like doing this because he’s a busy man (runs that office), but if three minutes of his time can save me an hour of travel, that’s a win. I get him to log on as admin. He goes to the batch file and makes the change. Just to double-check we did it right I ask him to go into Printer settings and double-check what I named the printer when I reinstalled it last night. Error. Sorry, administrator does not have access to the printer because it can not be found.

Fuck it. Looks like I’m traveling. If I thought I could get away with it I would stop at an Apple store on the way and buy a Mini to replace this piece of shit. Unfortunately we have one critical app that is running on… wait for it… DOS. Don’t even get me started.

(Note: Post title from this.)

[Insta-update -- As I'm writing this, the user called me to say that she could print again. It appears that the fix worked despite the printer being "lost". Once again -- What the Sam Hill is going on with this broken-ass software?]

[Update: Alternate Title: "There's a Hole in the Bucket. Just Fucket."]

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh