In November, I covered the ongoing legal battle between WPEngine and Automattic, the parent company of WordPress.com, focusing on the implications it had for the broader WordPress ecosystem. If you missed that update, you can find it here. On Tuesday the ruling made in the Injunction Hearing was made public. As a result, it is time to take another another look at the conflict and its potential ramifications for WordPress and its community.
The heart of the matter remains centered around a dispute between WPEngine’s Advanced Custom Fields (ACF) plugin, a popular tool for developers and Automattic’s actions surrounding it as well as economics. In this article, I’ll explore the latest developments, including why WPEngine and its parent company, Silver Lake, decided to reject a settlement offer, Matt Mullenweg’s defense of Automattic’s actions, and the judge’s recent orders that could reshape the way both companies interact with WordPress.org.
I forgot to mention in my previous article is that WPEngine and Silver Lake, despite pressure from Automattic, have chosen not to settle the dispute out of court. Automattic had offered what seemed like a reasonable solution: an 8% royalty payment or an agreement to allocate 8% of their workforce to contribute directly to WordPress’ development. This offer seems quite reasonable considering, as I mentioned in my last article, the idea behind open source is to create a community around the product and have the community contribute to the softwares success. This offer proves the heart of the matter in Matt Mullenweg’s eyes is money.
The refusal to settle, despite the potential for an agreement that would have avoided lengthy litigation, adds another layer of complexity to the situation. WPEngine likely felt that accepting the terms would set a dangerous precedent for their business model, which relies heavily on WordPress products and services. By rejecting the settlement offer, WPEngine is signaling that they are prepared to fight for their rights and protect their name in the community, potentially at great cost. Whether this decision will lead to a favorable outcome for WPEngine or not remains to be seen, but it is clear that the stakes have escalated.
On the other side of the dispute, Matt Mullenweg, founder of Automattic and a key figure in the development of WordPress, has defended the company’s decision to take over WPEngine’s Advanced Custom Fields (ACF) plugin page and support forum on WordPress.org. Mullenweg’s reasoning for this action was that it was necessary to remove commercial upsells that had been integrated into the ACF plugin. He also mentioned that the takeover was essential to resolve a security issue, though this justification has been met with some skepticism.
Mullenweg claims that by removing the upsells and controlling the plugin’s support forum, he and the WordPress.org team were acting in the best interest of the broader WordPress community. However, critics argue that this decision to take over WPEngine’s assets without consent was a clear overreach and a violation of the established norms of the WordPress ecosystem. The plugin, which had been developed and maintained by WPEngine for years was suddenly taken over in what many saw as a power grab.
While Mullenweg’s defense focuses on improving security and removing commercial upsells, it is clear that there is a larger power struggle at play. His management of the WordPress.org community has been growing steadily over the years, and this latest move to take control of an important plugin further solidifies their grip on the platform. Whether this is in the best interests of the community or simply a way to eliminate competition remains a matter of debate.
As this legal battle unfolds, the case has reached a critical juncture. On December 10th, a judge issued a ruling that directly addresses some of the core issues at play in the lawsuit. The judge ordered that Matt Mullenweg remove the controversial checkbox I referenced in my previous article. This checkbox, which appeared when users logged into WordPress.org, required them to affirm that they had no affiliation with WPEngine. The judge’s order to remove the checkbox is a significant step, as it underscores the court’s recognition that this requirement was problematic and likely overstepping Automattic’s bounds.
Additionally, the judge also ordered that Automattic stop blocking WPEngine’s resources from accessing WordPress.org. This was another key point of contention, as WPEngine has claimed that Automattic’s actions were preventing them from properly supporting their customers and contributing to the WordPress community. The judge’s ruling, which could have far-reaching implications for both companies, aims to restore a level of fairness and transparency to the situation. It’s a reminder that even powerful companies like Automattic can be held accountable for their actions, especially when they are seen as overreaching.
I learned today on Tech News Today that Megan Fox of Automattic commented to The Verge that the ruling was designed to maintain the status quo. Fox emphasized that the decision was made without the benefit of discovery, which means that the court did not have access to all of the relevant information before issuing the ruling. This comment reflects Matt Mullenweg’s frustration with the judicial process and his belief that the ruling may have been premature or incomplete. Without access to full discovery, Automattic argues that the decision could potentially be flawed and that the case should proceed to trial, where both sides can present a fuller picture of the situation.
As we look at the ongoing developments in this case, it’s essential to understand the broader implications for the WordPress ecosystem. WordPress, as an open-source platform, has thrived over the years due to its decentralized nature and the contributions of developers and businesses that operate in the space. The dispute between Automattic and WPEngine, however, has the potential to undermine this model, especially if one company gains too much control over the platform.
If Automattic is able to successfully assert its dominance over plugins and other key aspects of WordPress, it could lead to a shift in the balance of power within the ecosystem. Smaller businesses and independent developers may find themselves at a disadvantage, unable to compete with Automattic’s resources and influence. This could stifle innovation and reduce the diversity of solutions available to WordPress users.
Moreover, the dispute has also raised concerns about the future of the WordPress plugin marketplace. If Automattic is able to take control of high-traffic plugin pages and restrict competitors from accessing important resources, it could set a dangerous precedent for other companies operating within the WordPress space. This could lead to a more centralized, monopolistic environment where only a few players control the platform’s development.
To help illustrate the potential consequences of this lawsuit, consider a hypothetical situation in which Amazon decides to sue Apple if Apple were to stop using Amazon’s cloud services, AWS, and start building their own infrastructure. The analogy is relevant because, like Automattic, Apple relies heavily on external services—in this case, Amazon’s AWS data warehouses—to power iCloud. If Apple were to suddenly decide to create its own cloud infrastructure from scratch, it would not only disrupt its relationship with Amazon but also risk creating a new competitive landscape in the cloud services space.
Here’s the thing folks: The internet itself relies on a complex network of interdependencies, with many companies relying on each other’s infrastructure to deliver services. Just as Amazon’s AWS powers much of the internet, Automattic and WPEngine are both part of a delicate ecosystem within the WordPress world considering WordPress powers over 40% websites. If one company oversteps and disrupts this balance, it could lead to unintended consequences that harm not only the two companies involved but the entire WordPress ecosystem.
With that… the ongoing lawsuit between Automattic and WPEngine is, in many ways, a microcosm of this broader issue. Both companies are critical to the development and growth of WordPress, and their actions will have lasting effects on the platform. Whether this conflict will lead to a more centralized WordPress ecosystem dominated by Automattic or whether a more collaborative model will emerge remains to be seen. For now, we’ll have to wait and see how the legal process unfolds.
When you play with them you have a different understanding.