Comments on: WordPress Plugins should be Regulated

By: WordPress 2.5 Release Candidate 2 at YugaTech | Philippines, Technology News & Reviews

Sat, 29 Mar 2008 00:43:50 +0000

[...] This is a landmark development, IMO, as it helps resolve the problem of unsecured and buggy plugins. See my previous entry on why “WordPress Plugins should be Regulated“. [...]

By: Blogoloco - Win $250

Blogoloco - Win $250 — Sun, 27 Jan 2008 17:51:56 +0000

excellent post Abe. Pag libre, you don’t get it all in one package.

By: Blogoloco - Win $250

Blogoloco - Win $250 — Sun, 27 Jan 2008 17:48:51 +0000

That’s what we get for free.

By: yuga

yuga — Fri, 25 Jan 2008 22:51:03 +0000

@ Ian, it’s a start but it looks like the review is community driven and I don’t think the community is looking at it on the code-level but on the functionality level. So a plugin may get a 5-star rating because from the onset it works as intended, even if it’s poorly coded.

By: Ian

Ian — Thu, 24 Jan 2008 16:28:28 +0000

Isn’t being hosted in wordpress.org/extend already a form of imprimatur that, yes, WordPress recommends this plugin?

Looking at the conditions for being hosted there — it has to be GPL, it must not do anything “naughty” — WordPress core developers could probably raise the bar (yes, something akin to Mozilla QA sounds nice).

But in the end, since it’s open source, why not let the community decide (you know, lots of eyeballs on the code)?

By: jhay

jhay — Thu, 24 Jan 2008 13:05:36 +0000

This is a good start of something definitely positive in the WP community. Perhaps we should all blog about this as well. Like a campaign or something similar to the call for adhering to web standards.

Oh wait, there goes an idea for niche blog!

By: Shutter Box Philippines

Shutter Box Philippines — Thu, 24 Jan 2008 07:05:55 +0000

I’m not familiar with expression engine but I guess they should check out what the drupal community is doing. even the codes of submitted drupal plugins are audited to mae sure that it follow secure coding guidelines and it wont’t break drupal.

By: Jaypee

Jaypee — Wed, 23 Jan 2008 16:03:31 +0000

I was also thinking of writing something like this but I’m glad you did it. You’re right about this. WP should do something like Firefox does to it’s extensions or addons. When you install a Firefox extension you get that message telling if the extension is certifed by Mozilla or not. I really think this should be done to eliminate plugis with malicious code and to prevent further or future problems. Good post Abe!

By: Christian

Christian — Wed, 23 Jan 2008 15:49:07 +0000

Exactly, I once build a site based on a plugin that eventually became obsolete once a new WP version came out. Lesson learned, don’t build a site based on a plugin unless it’s “big” & supported like PodPress.

By: deuts

deuts — Wed, 23 Jan 2008 14:48:46 +0000

Yeah and before Automattic certifies the plugin, it should be a must that it should indicate at which WP version it is compatible, or better yet provide different plugin versions for different WP versions.

By: rod

rod — Wed, 23 Jan 2008 13:35:28 +0000

some of them are not even protecting their plugins folder

By: LiNTEK

LiNTEK — Wed, 23 Jan 2008 12:04:00 +0000

Hmmnnn…. WP should be the QA for these plugins, review bugs, check for vulnerabilities and have them fixed. Once tested and certified OK, then that is only the time users like us should download the plugins and use it for our blogs.

By: sylv3rblade

sylv3rblade — Wed, 23 Jan 2008 11:10:30 +0000

Hmm.. adapting Expression Engine’s attitude on addons/plugins would be nice.