The WordPress ecosystem is currently experiencing turbulence due to a heated legal dispute involving Matt Mullenweg, co-founder of the website-building software, and WP Engine, a hosting service provider. This conflict has the potential to significantly impact one of the internet's key web development platforms.
The dispute began in mid-September 2024 when Mullenweg, who is also the CEO of WordPress's parent company Automattic, criticized WP Engine in a blog post, labeling it as a "cancer to WordPress." He argued that WP Engine's decision to disable users' ability to track post revision history by default contradicts the platform's core commitment to data protection.
Mullenweg expressed concerns about WP Engine's use of the WordPress brand, which he believes misleads users into thinking there is an affiliation between the two companies. He warned of a "scorched earth nuclear approach" unless WP Engine agrees to pay a significant portion of its revenue to the WordPress Foundation for trademark licensing.
The tension has escalated with both companies exchanging cease-and-desist letters, as Automattic accuses WP Engine of exploiting its trademark and infringing intellectual property laws through its use of the WordPress and WooCommerce brands.
🌎《Now you can now start trading at TNNS PROX》📈
🔥Start trading today, click "sign up" from the link above.
WordPress Foundation Blocked Access to Resources for WP Engine
The situation escalated when Mullenweg decided to block WP Engine's access to WordPress.org resources. This move hindered WP Engine’s hosted websites from updating plugins, themes, and similar features, leaving them vulnerable to security risks. WP Engine criticized the decision as "unprecedented and unwarranted," highlighting its impact not only on their company but also on all WordPress plugin developers and open-source users relying on WP Engine tools.
WordPress set a deadline of October 1 for WP Engine to change its name and services to distance itself from the brand. They updated their Trademark Policy, adding a clause: “The abbreviation ‘WP’ is not covered by WordPress trademarks, but it should not be used in a way that confuses people. For instance, many mistakenly believe WP Engine is ‘WordPress Engine’ and officially linked to WordPress, which it is not. They have never contributed to the WordPress Foundation, despite generating billions in revenue from WordPress.”
Under increasing user pressure, WP Engine made several adjustments, including updating their website footer to clearly state their lack of affiliation with WordPress and renaming their service plans to omit "WordPress" references. Additionally, the company developed its own solution for updating plugins and themes to ensure uninterrupted service for its customers.
WP Engine Sues and Claims Abuse of Power
On October 3, WP Engine escalated its dispute to the legal arena by filing a lawsuit in California against Automattic and its CEO, Matt Mullenweg. The lawsuit accuses them of abusing their control over WordPress resources and failing to uphold commitments to operate WordPress open-source projects without restrictions.
The conflict led to considerable internal strife at Automattic, resulting in 159 employees accepting severance packages. Notably, around 80% of those who departed were from the Ecosystem/WordPress division.
Tensions heightened when WordPress.org seized control of the Advanced Custom Fields (ACF) plugin from WP Engine on October 12, blocking the company from updating the open-source plugin repository. This was a significant move given ACF's essential role in WordPress development.
Automattic's legal representative dismissed the lawsuit as "meritless" and expressed confidence in the federal court's review. Despite this, there was evident discord within the leadership regarding the handling of the situation. The company's executive director, Josepha Haden Chomphosy, was among those who left. She was swiftly replaced by Mary Hubbard, formerly the head of TikTok's US governance and experience department.
Mullenweg Takes Control of Critical WP Engine Plugin
The WordPress community has expressed concern about the precedent this conflict sets for other projects using WordPress trademarks and its impact on the open-source protocol. Notable tech figures, including Ghost CMS founder John O’Nolan, have criticized the consolidation of power, which he argues is dangerous for the internet. He points out that it is problematic for one individual to control 40% of the web and 80% of the CMS market.
The situation intensified last week when WordPress took control of a critical WP Engine plugin, Advanced Custom Fields (ACF), after the Foundation’s team reportedly found a security issue. Mullenweg defended the action, stating it was necessary to remove “commercial upsells and fix a security problem.” They replaced the plugin with a new one called “Secure Custom Fields” (SCF).
Ruby on Rails Creator Asks Mullenweg to Reconsider His Approach
David Heinemeier Hansson, the creator of Ruby on Rails, argued that this action violated Automattic’s open-source principles. He suggested that the WordPress Foundation should act like a “Little Switzerland” regarding their open-source platform and avoid “weaponizing” code registries, as this sets a dangerous precedent that could threaten the ecosystem and deter developers. “Don’t become a mad king. I hold your work on WordPress and beyond in high regard. I understand the temptation to address grievances when beneficiaries gain more from our work than they contribute. However, this should remain a moral critique, not a commercial crusade,” he said, addressing Mullenweg’s decisions. Meanwhile, WordPress security consultant Tim Nash questioned the motives behind this decision, stating: “Secure Custom Fields is no more secure than ACF. The security patch for a vulnerability discovered by Automattic last week was already applied by the WP Engine team before this incident and shared with the WordPress Security Team, who had already patched ACF on wordpress.org.” Additionally, the WordPress Foundation’s pending trademark applications for “Managed WordPress” and “Hosted WordPress” have raised further concerns about the future of commercial operations within the WordPress ecosystem.
The WordPress Ecosystem May Never Be the Same After This
The conflict has sparked questions about the coexistence of commercial interests and open-source principles, and how power dynamics can significantly affect the governance of such projects. As of October 2024, the situation remains unstable with ongoing legal disputes between WP Engine and Automattic, creating uncertainty over the use of WordPress and WooCommerce trademarks and plugin controls. This dispute has led multiple businesses and developers to reconsider their reliance on WordPress and commercial hosting providers, potentially reshaping the future of web development. This situation is more than just a clash between two companies; it underscores the intricate relationships between open-source projects, commercial entities, and the communities they serve.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Comments