The world of WordPress, one of the most popular technologies for creating and hosting websites, is going through a very heated controversy. The core issue is the fight between WordPress founder and Automattic CEO Matt Mullenweg and WP Engine, which hosts websites built on WordPress.
WordPress technology is open source and free, and it powers a huge chunk of the internet — around 40% of websites. Websites can host their own WordPress instance or use a solution provider like Automattic or WP Engine for a plug-and-play solution.
In mid-September, Mullenweg wrote rel=”nofollow” href=”https://wordpress.org/news/2024/09/wp-engine/”>a blog post calling WP Engine a “cancer to WordPress.” He criticized the host for disabling the ability for users to see and track the revision history for every post. Mullenweg believes this feature is at the “core of the user promise of protecting your data” and said that WP Engine turns it off by default to save money.
He also called out WP Engine investor Silver Lake and said they don’t contribute sufficiently to the open source project and that WP Engine’s use of the “WP” brand has confused customers into believing it is part of WordPress.
The legal battle
In reply, WP Engine sent a cease-and-desist letter to Mullenweg and Automattic to withdraw their comments. It also said that its use of the WordPress trademark was covered under fair use.
The company claimed that Mullenweg had said he would take a “scorched earth nuclear approach” against WP Engine unless it agreed to pay “a significant percentage of its revenues for a license to the WordPress trademark.”
In response, Automattic sent its own cease-and-desist letter to WP Engine, saying that they had breached WordPress and WooCommerce trademark usage rules.
The WordPress Foundation also changed its Trademark Policy page and called out WP Engine, alleging the hosting service has confused users.
“The abbreviation ‘WP’ is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is ‘WordPress Engine’ and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress,” the updated page reads.
WP Engine ban, community impact, and trademark battle
Mullenweg then banned WP Engine from accessing the resources of WordPress.org. While elements like plug-ins and themes are under open source license, providers like WP Engine have to run a service to fetch them, which is not covered under the open source license.
This broke a lot of websites and prevented them from updating plug-ins and themes. It also left some of them open to security attacks. The community was not pleased with this approach of leaving small websites helpless.
In response to the incident, WP Engine said in a post that Mullenweg had misused his control of WordPress to interfere with WP Engine customers’ access to WordPress.org.
“Matt Mullenweg’s unprecedented and unwarranted action interferes with the normal operation of the entire WordPress ecosystem, impacting not just WP Engine and our customers, but all WordPress plugin developers and open source users who depend on WP Engine tools like ACF,” WP Engine said.
Disclaimer
We strive to uphold the highest ethical standards in all of our reporting and coverage. We StartupNews.fyi want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.
