The following is a non-exhaustive list of things you can do to get your plugin rejected or removed from the WordPress.org plugin directory.
Yes, this is tongue-in-cheek. This is a list of things NOT TO DO.
- Give it a license that is incompatible with WordPress’ license.
- Host your plugin elsewhere, and only use the WordPress.org plugin listing as a pointer to that.
- Use base64 encoding to hide your plugin code or obfuscate HTML that you’re injecting into people’s blogs.
- Insert SEO spam links into people’s blogs (like <a href=”http://example.com/”>video poker</a>).
- Insert external links (like a credit link, <a href=”http://example.com/”>My Awesome Plugin by Awesome Sauce</a>) into their blog without explicitly asking their permission, or make the default option be to insert the link.
- Load portions of the code from an external site for no valid reason, or use any other trick to work around #3, #4 and #5.
- Harvest people’s e-mail addresses or require registration to activate the plugin.
- Explicitly state or imply that users of the plugin must pay you money in order to use the plugin.
- Make the plugin a “requirements check” or bootstrapper for some other plugin, hosted elsewhere. See #2.
- Make it do something illegal.
- Make it do something sneaky, underhanded, or otherwise dishonest or immoral. Maybe a plugin that disables all plugins by a plugin author you don’t particularly like. Harvest the user’s password. Use your imagination!
Again, this is a list of things not to do. It is not comprehensive. Be cool, think of how your plugin benefits its users, and write awesome plugins.
