WordPress moves to ban WP Engine from accessing its resources
We’ve updated our story on the WordPress v. WP Engine feud with the latest twist: More than 150 Auttomatic employees quit in protest.
WordPress co-founder Matt Mullenweg is mad.
“WP Engine needs a trademark license, they don’t have one. I won’t bore you with the story of how WP Engine broke thousands of customer sites (October 31, 2024) in their haphazard attempt to block our attempts to inform the wider WordPress community regarding their disabling and locking down a WordPress core feature in order to extract profit. What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.“WordPress blog (bold in the original)
This seems to mean that sites using WP Engine cannot install plugins or update their themes (full disclosure, MarTech.org is among them). Mullenweg is CEO of Auttomatic which counts WordPress as one of its products.
Cease and desist. Cease and desist letters are going back and forth between the leading CMS and the hosting platform. Mullenweg had been complaining loudly about trademark violations, alleging that WP Engine was illegitimately monetizing them while misleading consumers to believe that there is a formal affiliation between WP Engine and WordPress.
WP Engine served a cease and desist letter on WordPress saying it complies with trademark law. Auttomatic responded a day later with its own cease-and-desist letter, again alleging unauthorized use of WordPress’s intellectual property leading to “unjust enrichment and undue profits.”
This all happened this week, leading up to the breaking news of the block on WP Engine.
Please de-escalate. As WordPress users weigh in, the general sense of their comments seems to be that WordPress’ rhetoric is getting out of hand. “Absolutely ridiculous. The letters WP are used on hundreds of plugins and themes, and have for decades without issue. Even the WordPress Foundation’s own Trademark Policy page acknowledges they have no case: “The abbreviation ‘WP’ is not covered by the WordPress trademarks.”
Cody Bromley wrote on Threads: “Absolutely ridiculous. The letters WP are used on hundreds of plugins and themes, and have for decades without issue. Even the WordPress Foundation’s own Trademark Policy page acknowledges they have no case: “The abbreviation ‘WP’ is not covered by the WordPress trademarks.”
Why we care. For Mullenweg this is clearly personal: “WP Engine is free to offer their hacked up, bastardized simulacra of WordPress’s GPL code to their customers…” For WP Engine it’s surely an existential issue.
For all the users, for all the marketers relying on a WordPress instance that draws on WP Engine’s resources, it just makes life that little bit more difficult.
The post WordPress moves to ban WP Engine from accessing its resources appeared first on MarTech.
About the author
Kim Davis is currently editor at large at MarTech. Born in London, but a New Yorker for almost three decades, Kim started covering enterprise software ten years ago. His experience encompasses SaaS for the enterprise, digital- ad data-driven urban planning, and applications of SaaS, digital technology, and data in the marketing space. He first wrote about marketing technology as editor of Haymarket’s The Hub, a dedicated marketing tech website, which subsequently became a channel on the established direct marketing brand DMN. Kim joined DMN proper in 2016, as a senior editor, becoming Executive Editor, then Editor-in-Chief a position he held until January 2020. Shortly thereafter he joined Third Door Media as Editorial Director at MarTech.
Kim was Associate Editor at a New York Times hyper-local news site, The Local: East Village, and has previously worked as an editor of an academic publication, and as a music journalist. He has written hundreds of New York restaurant reviews for a personal blog, and has been an occasional guest contributor to Eater.
(8)
