Skip to content


The Rejection by Andreas WintererDear Reader,

One of the biggest complaints I hear about WordPress is that yes, you can choose from thousands of plugins, but many of them are crap. Because there was no barrier to entry, many of them were poorly coded and could even introduce security vulnerabilities to your site. I recently found out the hard way that WordPress is moving to change that. :)

First, they have been retiring old and unmaintained plugins for a while now. Thankfully, that includes all the plugins I wrote back in the 1.5-1.9 days. :) More importantly though, there is now a code review before accepting new plugins. This is a very good move on their part and I applaud them for this move.

There is a small problem though. They don’t seem to have published anything on what is acceptable/unacceptable in a plugin. In discussing my particular plugin with the reviewer, it seems the rules are kind of fuzzy as to what gets accepted or not, and they seem to be changing.

Overall, I think that a code review process is a very positive move for the WordPress ecosystem. It would be nice however, if the review team published the current rules. Even if those rules change, a current set of rules would help make sure that plugin developers don’t waste time and effort on plugins that won’t be accepted.

If these guidelines are already available, linking to them from “Writing a Plugin” would be apprecaited.

Well done, WordPress!

Until next time,
I <3 |< =C= p.s. I am working on updating my plugin to change the reported problem so that hopefully it will be accepted next time. (fingers crossed) :) Photo Credit: The Rejection by Andreas Winterer. Used under Creative Commons License.

12 thoughts on “WordPress REJECTED MY PLUGIN!

  1. Hi Peter!

    My plugin – a developer plugin – was dependant on another plugin. They have recently (?) changed the rules and are not allowing developer only plugins and they do not allow plugins that require other plugins.

    I’m re-writing my plugin to encapsulate the features I was using from the other developer only plugin.

    Thanks for the comment!

  2. Interesting that they’re requiring plugins to be self-contained. On the one hand, it extricated plugins out of Dependency Hell, but on the other, there *are* dependency managers out there…which WP likely can’t use ‘cuz they’ve gotta run on two-bit shared hosting still.

    Maybe this will result in more of a push to integrate that dev-only plugin functionality into WP core, if it’s more universally needed. Which would probably be a good thing anyway.

    I *am* glad to see that WP is moving away from its Wild West approach to plugin dev, at least for officially sanctioned plugins…seems like they’re “growing up” a bit along with the rest of the PHP community (and yes, I realize that Automattic was using nginx with PHP since before it was cool, so they were ahead of the curve on some stuff).

Comments are closed.