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.
Jon Henshaw | @henshaw | |
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.
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
The news of Youngblood’s experience sparked several threads on Twitter debating whether or not Automattic was claiming WP as its trademark. It was determined that it wasn’t a trademark dispute. Instead, the confusion was caused by the language used in the plugin directory code.
Mika Epstein, a regular contributor to WordPress, created a ticket to improve checks on non-viable plugin names to prevent abuse. In the ticket, she stated:
Currently the plugin directory code has a very basic check for disallowed terms in plugin names, including a number of restricted terms as determined by trademark owners. This has the flaw of ‘lumping together’ reasons why a plugin name is not permitted, causing confusion to the community.
Epstein went on to explain the reason for the checks, which are to stop plugin makers from exploiting the submission process and later adding the name WordPress to their plugin name.
Shortly after Epstein created the ticket, a WordPress spokesperson responded to our request to comment on this story. They told Coywolf News that “wp- recently got added to automated checks rather than manual checks and that wp- is monitored in plugin names to help prevent the use of a common loophole.” They also reiterated what Epstein stated in her ticket: “It is not uncommon for a plugin developer to use wp- to get plugin approval, only to later change the display name to WordPress.”
Additionally, the spokesperson clarified their position on “WP” as a trademark, which echoed what’s published on the WordPress Foundation Trademark Policy page.
WordPress Foundation holds the WordPress trademark, not Automattic. The trademark policy grants use of the ‘WordPress’ name and logo in specific cases, but not as part of a product, project, service, domain name, or company name. The WordPress trademark does not cover the abbreviation “WP,” and you are free to use it in any way you see fit.
If you like web technology and marketing news, along with the occasional random stuff, then this is the newsletter for you. No ads. No sponsors. No spam. Only interesting and timely stories. Unsubscribe anytime.
Jon Henshaw
Jon is the founder of Coywolf and the EIC and the primary author reporting for Coywolf News. He is an industry veteran with over 25 years of digital marketing and internet technologies experience. Follow @henshaw
✿ This site uses privacy-first Fathom Analytics and does not track or collect personal data.
© 2017-2022 Coywolf LLC All Rights Reserved – Privacy Policy – Terms of Service
Coywolf and the Coywolf logo are registered trademarks of Coywolf LLC
Scan QR code to view article online
