The WordPress Plugin Review Team is rejecting plugins that use WP in the name and slug. The messaging and code made it appear like a trademark issue, but it wasn’t. A ticket has been created by a WordPress contributor to remove the confusion.
Joe Youngblood, a digital marketer from Dallas, TX, had an unpleasant surprise on Friday the 13th. He was horrified after submitting a new WordPress plugin to the WordPress Plugin Directory and it was auto-rejected. The rejection message stated th…….
More On RSS Feeds
- Meghan Markle Reportedly Got Her Wikipedia Page Changed After She Met Prince Harry - MarieClaire.com
- Madison names Morrison as the next Athletic Director effective immediately - 953wiki.com
- Sola Onayiga Wiki, Biography, Age, Husband, Death, Age, Parents, Kids, Family, Net Worth & More - News Unzip
- Pop Smoke Height, Weight, Age, Wife, Net worth, Parents, Siblings, Wiki, Biography & More - News Unzip
- Which Free Digital Marketing Course Is Right for You? - CMSWire
Joe Youngblood, a digital marketer from Dallas, TX, had an unpleasant surprise on Friday the 13th. He was horrified after submitting a new WordPress plugin to the WordPress Plugin Directory and it was auto-rejected. The rejection message stated that the plugin could not include WP in the plugin name.
In correspondence with the WordPress Plugin Review Team, a team member told Youngblood that they were explicitly instructed to prohibit the use of WP in plugin names.
Email reply from WordPress Plugin Review Team – Image Credit: Joe Youngblood via Twitter
Youngblood tweeted about his experience on Twitter and caught the attention of a fellow digital marketer, Andy Beard. Beard was able to quickly find when and where the change was made.
Beard found that approximately three months ago, a WordPress contributor added
wp- to their automated trademark checking code. The code specifies that WP is a trademark of Automattic and can’t be prepended to a plugin’s slug name.
After further investigation, Youngblood posted a tweet thread about everything he had learned about WordPress blocking plugins from using WP.
Here’s everything I know so far about this “WP” issue with WordPress
- Roughly 3 months ago The WordPress Foundation requested that the volunteer team block any plugins from using the term “WP” at the start of their name.
- The WordPress Foundation does not own any legal rights to the term “WP” only “WordPress”. WP is owned as a trademark in a few industries by @WhistlePigRye and Donegal Insurance for their internal software “Write Pro”
- WordPress plugin support told me that it was a good thing I couldn’t use the plugin name I had invested a lot of time and money into because it was bad for SEO anyways.
- The block list as uncovered by @AndyBeard includes a few well known WordPress plugin names including WP Mail SMTP, which ironically starts with “WP”.
- Whoever is at plugin support told me that “there are various legal teams hashing it out”, but there isn’t much to hashout since neither The WordPress Foundation nor Automattic own the trademark to “WP”.
- For those unaware, in 2010 the founder of WordPress Matt Mullenweg established The WordPress Foundation which took ownership of the trademark “WordPress” and declared that any developer could use “WP” in any way they wished. Many gave up domains with “wordpress” in them.
- It has been commonplace for over a decade that WordPress developers making a plugin start with the term “WP” to signify that it is a WordPress plugin. This convention is also used by hosting …….