{"id":876,"date":"2008-08-08T17:13:30","date_gmt":"2008-08-08T15:13:30","guid":{"rendered":"http:\/\/planetozh.com\/blog\/?p=876"},"modified":"2008-08-08T17:35:08","modified_gmt":"2008-08-08T15:35:08","slug":"2008-plugin-competition-review-part-2-of-2","status":"publish","type":"post","link":"https:\/\/planetozh.com\/blog\/2008\/08\/2008-plugin-competition-review-part-2-of-2\/","title":{"rendered":"2008 Plugin Competition Review, Part 2 of 2"},"content":{"rendered":"

Here is part 2 (of 2) of my "reviewing", mostly from a plugin coder's point of view, the plugins running in the WordPress Plugin Competition<\/a>.<\/p>\n

Please, please and puh-leaaase, if you are a contestant and if you didn't read Part One<\/a>, do read it before you proceed to part 2. There is a mandatory disclaimer<\/em> that you and me don't want you to miss before you read any comment I could have made on a plugin of yours :) Thanks in advance. Now, let's go:
\n<\/p>\n

Picture Increment Cron System<\/h2>\n

Picture Increment Cron System<\/a> turns a collection of pics inside a directory into one post a day<\/em>
\nFun idea. Alas, the plugin is encrypted with Zen Guard<\/a>, which makes its source completely obfuscated and unreadable, which is in itself enough reason for me not to install a plugin. By the way, I think this infringes the Plugin Competition guidelines, as well as the WordPress plugin repository, which require plugins to be GPL compatible.
\nYuck. Sucks.<\/p>\n

Post Tabs<\/h2>\n

post Tabs<\/a> splits posts into a tabbed interface<\/em>
\nThat is a rather cool idea that will probably find its audience. I could easily use something similar on my blog, for instance on plugin pages where I would have a first tab about the plugin concept, a second tab about detailed documentation, then a tab about download and install instruction, and finally a tab with a FAQ.
\nGood stuff: all the admin part is in a separate file that doesn't load in memory when someone views the public part of the blog. The 13 saved options of the plugin are all in the same DB entry. The code is fairly clean and well commented.
\nWeird stuff: all the javascript is old school code that seems to have escaped from a 1998 web page. I mean, I thought everybody was in love with jQuery nowadays, right? The color picker is pretty ugly too, with a very limited set of colors.
\nBad stuff: hardcoded path to the plugin directory, nothing is sanitized or checked before being stored in options.
\nImprovable stuff: all the javascript could be improved and made less obstrusive, with behaviors added to span elements instead of making up links with href="javascript:something"<\/em>. This would also allow for more degradable stuff when javascript is turned off, instead of having hidden tabs you cannot read. The whole stuff could be more "semantic" too: having an unordered list of tab names followed by divs containing the tab contents seems ugly to me and will be unreadable when printed or with a screen reader. All the javascript should load only if a post on the page needs it, instead of being unconditionally added into the page <head>.<\/p>\n

Role Scoper<\/h2>\n

Role Scoper<\/a> lets you define roles and groups to manage privileges amongst several users<\/em>
\nThis seems to be a very ambitious plugin that will seriously help multi user blogs. To be honest I didn't test it and gave a quick glance at the code, which looked clean and very well commented, but this is obviously not a plugin you can really judge in a few minutes.
\nWhat I did like though, and hence this mini review despite my lack of insightful comments, is the explanations, their content and their tone. Very well put, clear, detailed but not overwhelming. Or maybe it's just that this plugin rang some bell in me? I'm pretty sure that this plugin will be something I'll remember and point to when I get questions about role managing.<\/p>\n

SEO Smart Links<\/h2>\n

SEO Smart Links<\/a> automatically interlinks your posts and pages on keywords matching category, or tags, or posts names<\/em>
\nTo be honest, whenever I see a plugin with "SEO" in its name, I want to trash it. While a small fraction of people truly understand SEO, everybody and their mother seem to have awesome ideas and invent new tricks. Want to make a popular plugin? Use this pompous keyword and you're almost done.
\nOK, enough for the rant, what about this plugin anyway ?
\nCoding style is so-so, with a lot of indenting inconsistencies and no comment to help the reader understand what's going on. The plugin seems to add between 1 and 4 queries to every post displayed, depending on options, but also seems to hopefully use WP built in query cache to reduce impact.
\nGenerated links are either with target="_blank"<\/em>, which is a pain to me as a reader, or nofollowed<\/em>, which has exactly zero SEO impact. I don't get why on Earth you would chose between these two modes and why they should be mutually exclusive.
\nThe plugin seems to be a potential candidate for update problems via WordPress' notifier: depending on where you look (plugin name, directory or plugin filename), the name is either "SEO Smart Links", "SEO Links" or "SEO Automatic Links", which is not the best way to ensure that WP will always detect when a new version is available (at least according to my empiric observations<\/a>)
\nOn the plus side, I'll mention that all options are stored within, everybody says it loud with me, just one DB entry.
\nAll in all and despite my negative remarks, probably not a bad plugin. I just can't help having negative feelings towards the implied "man you're gonna get so goodly rank0red in Google you won't beeleeeeve it !!!1"<\/p>\n

Show Me Options<\/h2>\n

Show Me Options<\/a> detects the URL to a plugin option page when you activate it (no more wandering through Settings then Manage then Plugins to find the darn submenu)<\/em>
\nThis plugin is a gem.
\nEven if you shouldn't really need<\/em> it (I mean, you're all using Admin Drop Down Menus<\/a> now, right? so searching for a submenu is just a matter of hovering), this is the kind of short plugin that provides just a little help, in just one place, just sometimes, but that will make the whole experience more pleasant. This is the kind of plugin that adds features that don't look like plugin features: they look like something WordPress does, or should do, out of the box.
\nI would move everything to a conditionally included file that would load only if (is_admin()), but the plugin is so short that it's negligible. I would also hook with 'load-plugins.php' instead of 'admin-head'. The biggest complaint I have here would be to add more inline commenting, but again, this is a short plugin.
\nThe whole job is done in a smart way. Or at least it must be fairly smart, since I cannot think of any other simple way to do so, and I probably would have not find any simple way at all to do it if someone asked me to code something similar.
\nThings are not perfect, since the plugin will be fooled by plugins which add multiple pages (one under Manage and another one under Settings for instance) but things will be fine in most cases.
\nOverall: a simple feature, a short plugin, a great result. No fancy stuff, no amazing interface, nothing that looks like it needed 3 months of work and a ton of files, just a simple idea to improve a simple task with a very smart piece of code. I really like it.<\/p>\n

Simple Flash Video<\/h2>\n

Simple Flash Video<\/a> does something with Flash videos. I guess.<\/em>
\nI didn't review nor try this plugin, but want to highlight something very important when designing a plugin: once you're pleased with your code and the features, don't botch up the packaging<\/em>, ie the page that will "sell" the plugin. Don't let people (or competition judges) guess what your plugin is about, tell them<\/strong>.
\nThis plugin page lacks a clear brief intro that will say "this plugin does this and that, and it's cool because of this and this". All you see is at first glance is irrelevant information, and features. Features are important to highlight, but it's not the first thing you want to tell. The first stuff your page has to be about is… what your plugin is about. Starting by features is like saying to a potential customer "my product has 4 wheels!" when this customer doesn't even know if you're talking about a car, a quad bike or a wheelchair.<\/p>\n

Snazzy Archives<\/h2>\n

Snazzy Archives<\/a> displays your blog archives as a compelling mosaic of text and images<\/em>
\nThe result of this plugin is quite aesthetic, inspired by the way Tumblr<\/a> displays post archives. The plugin in itself is mostly CSS and JS, the PHP part of it is minor and trivial, yet neatly done: using shortcodes, adding JS and storing options are done the way they should.
\nThe Javascript work might be a bit incomplete, as for instance all the "toggle" links seem to do nothing on my Firefox, but I have to admit that the result is pretty anyway.
\nHere on this blog, the result out of the box was totally terrible, so I think depending on your theme you might have some CSS work for better integration. Will look best on blogs embedding a lot of images.<\/p>\n

Tabbed Widgets<\/h2>\n

Tabbed Widgets<\/a> enhances sidebar widgets with visual "Tabs" or "Accordions" effects<\/em>
\nAs far as I can tell about the code, this is mostly state of the art coding. Everything is clean, wrapped into a class, with correct use of API functions to inject javascripts and everything. The few improvements I can suggest are the use of nonce functions and sanitizations of options before they're stored, a more WP 2.6 compliant way of guessing the plugin's path, and moving admin stuff into a separate file that won't load in memory when viewing a blog page.
\nAs expected from anything by Kaspars, the interface of the plugin is sexy and appealing. I would suggest a more dynamic way to add widget wrappers, instead of having by default 8 blocks each containing 6 rows. As of now, that makes a lot of empty spaces, and a gazillion "Update Options" button that might be a bit scary.
\nI don't exactly have a smart suggestion about it, but I think it would be better if the whole stuff was more integrated with the Widgets page, rather than having to deal with 2 pages (Widgets and Tabbed Widgets). Something like adding at the bottom of the Widgets page a field for "How many Tabbed widgets to you want?" and creating new widgets accordingly.
\nAll in all, a very clean and pleasant plugin.<\/p>\n

tWPtter<\/h2>\n

tWPtter<\/a> allows you to publish short posts via a widget or a page within your blog, or via email<\/em>
\nThe first things that popped in my head were: Wow, fun name, how the f*ck you pronounce that? Wow, totally cool logo. Things start really better when you go "wow" on first sight :)
\nThen I started to "de-wow" a bit since I could find a download link on the page. Honestly, I had to view the page source, search for "download", to find out that the tiny link was totally hidden under an ad. There has to be a better way to do this!
\nThe code is compact, more or less randomly indented and difficult to read. The usual mistakes are there: each option generates one entry in wp_options, plugin path is hardcoded, the author didn't understand how plugin translation works<\/a> (it's not just using _e($string)<\/tt>)
\nThe plugin is cute and probably fun to use, but from a coder's perspective could be improved a lot. Which wouldn't make it any cuter or more fun to use, actually, but you know, geeks, they like when everything under the hoods is neat and ordered :)<\/p>\n

Vent<\/h2>\n

Vent<\/a> is an event manager that uses the scheduled posts functionality to manage future events<\/em>
\nThis plugin looks like a piece of serious work, in a field (managing events) that will certainly meet an audience.
\nVery nice code, clean, commented, structured. As everything is already splitted into a public and an admin class, it would make sense to even put these classes into separate files so the admin functions wouldn't load and compile when viewing the blog. Really nothing more to say about the code as this is obviously a pretty big work that can't be evaluated in a few minutes.
\nWhat I want to outline here, once again, is the plugin page<\/a>. Clean and clear, with a small screenshot of all the key aspects and features of the plugin: by the time you've read the page, you already have the feeling you've started using the plugin.
\nThis really looks like an impressive plugin, with smart integration of its features into the existing admin pages (namely, the Write page)<\/p>\n

WP 125<\/h2>\n

WP 125<\/a> is a 125x125pixels ads management plugin<\/em>
\nCode is ugly and totally unindented, if such a word exists. Let me be clear on something that may not be obvious for everybody: having clear, commented and neatly indented code is not just a geek useless odd mania, it's a must have for maintainable code. A few months after you've written a plugin, you mostly forgot how things run, how you handled this damn problem or how super smart was your super long regexp. After a few months, you need<\/strong> your code to be easily readable.
\nCoding wise, the plugin seems to be improvable in several areas. There's a click tracking function that stores into a MySQL table something right from the $_GET parameter without any sanity check, which is a loud call for exploit. There's an install function triggered by plugin activation, that's fine, but the install file gets included anyway on every page view, that's a waste. Same thing for the admin menu stuff: they are in a separate file, fine, that's always included, not fine.
\nThe plugin creates 2 tables, one for ads and one for settings. Having a table for ads is probably a good idea, since you'll probably want to keep track of a lot of thins. But creating a table for options doesn't look like a good idea to me: this will add an extra query on every page view, to read options, and this query would be avoided using wp_options to store them. Queries are expensive, always code as if you were paying for each one<\/em>.
\nFeature wise, I think the plugin lacks a bridge with Paypal to automate billing, in order to truly save time on cumbersome tasks.<\/p>\n

WP Comment Remix<\/h2>\n

WP Comment Remix<\/a> adds functions and options to the default WordPress commenting system<\/em>.
\nThis plugin appears to borrow some code and ideas from my own Absolute Comments<\/a> as well as throwing a few other features in the mix.
\nThe lack of file and directory structure in the archive is a bit overwhelming: that's 20 files in the same directory, JS, CSS, .mo and .php all partying together. I find things easier to maintain and understand when files are logically put and ordered. Other than that, the code is very clean and well commented.
\nThis is by far a too complex plugin to be reviewed here: too much code to ponder, too much features to test, a two paragraphs review wouldn't do it justice, and given that I'm the author of a plugin in this field, I have a pretty established opinion of what lacks and what would be cool. I will definitely have a later deeper look at this plugin when I have some time (maybe I'll end up borrowing a few ideas as well!) but after a 3 minutes run on my test blog, I gave it its 5 stars.
\nGiven the audience this plugin meets (basically: anyone with a WP blog), this well may be a winner for the plugin competition.<\/p>\n

WP Easy Uploader<\/h2>\n

WP Easy Uploader<\/a> lets you upload themes, plugins and anything from within WordPress<\/em>
\nCode looks serious at first glance: clean, using nonces and paying attention to user privileges, things that are a must when you are dealing with a plugin that, basically, will let you overwrite your wp-config.php if you say so.
\nThe PEAR files inclusion may be troublesome on a few installs because of the way they are included (not using a full path to the files, but instead toying with ini_set()<\/em>, which can be unavailable for security reasons). The choice of getting some PEAR library files to handle some parts of the job seems sensible to me, as they are probably fairly tested, secure and maintained.
\nThe plugin might lack some file browsing functions (like, when you want to delete or move something you've just uploaded) but that would broaden its actual scope (it's supposed to be just an uploaded after all).
\nOverall : a plugin I would probably not use or recommended because of the scary factor (any security hole in this plugin would be disastrous) unless it would go through a serious security review, but this does really look like a very nice job.<\/p>\n

WP Wall<\/h2>\n

WP Wall<\/a> adds a commenting "wall", just like in your sister's Facebook profile<\/em>
\nYet another plugin from Vladimir Prelovac who appears to be running something like 285 plugins in this competition.
\nRegarding the plugin code, same comments as from previous Vladimir's plugins apply (read for instance my thoughts on Live Blogroll<\/a>).
\nThis wall uses the commenting system to handle replies: that means that spam, moderation and managing in general will be done by WP and any Comment plugin you may run, which is a smart choice. Walls are an easy target for abuse and spam, so you'd better not try to re-invent the wheel here.
\nIf I had to use a Wall plugin, or when asked about one, I'll head to this plugin.<\/p>\n

And that's it<\/h2>\n

Overall it's been fun to have a look at all the plugins. I like to compare how coders do things and I would have done them, and how ideas and codes can cross-pollinate to get better.<\/p>\n

Thanks for reading if you did, but first of all thanks for participating in the contest and for coding plugins. And of course, thanks to the contest staff, I know how hard it will be to judge and rate all the plugins. This competition far the best moment of the plugin year, I hope I'll be able to throw some plugins in next year!<\/p>\n","protected":false},"excerpt":{"rendered":"

Here is part 2 (of 2) of my "reviewing", mostly from a plugin coder's point of view, the plugins running in the WordPress Plugin Competition. Please, please and puh-leaaase, if you are a contestant and if you didn't read Part One, do read it before you proceed to part 2. There is a mandatory disclaimer […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[259,85,63,245],"class_list":["post-876","post","type-post","status-publish","format-standard","hentry","category-published","tag-competition","tag-plugins","tag-review","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/876","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/comments?post=876"}],"version-history":[{"count":0,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/876\/revisions"}],"wp:attachment":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/media?parent=876"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/categories?post=876"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/tags?post=876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}