Citing ongoing legal tensions with hosting provider WP Engine, Automattic has announced the suspension of several key free services on WordPress.org. This decision, made by founder Matt Mullenweg, is expected to disrupt workflows for developers and users alike during a critical time for the community.
Key Takeaways
- Automattic suspends new account registrations, plugin and theme submissions, and more.
- The suspension is a response to a legal battle with WP Engine.
- The conflict escalated after Automattic forked the Advanced Custom Fields plugin.
- A federal judge has intervened, ordering Automattic to reverse certain actions.
Background of the Conflict
The relationship between Automattic and WP Engine has been strained for years, but tensions escalated significantly in September 2024. During the WordCamp conference, Mullenweg publicly criticized WP Engine, calling it a "cancer" within the WordPress community. This public denouncement set the stage for a series of contentious events.
In October, Automattic forked the Advanced Custom Fields (ACF) plugin, which allows developers to add custom fields to WordPress edit screens. This move was seen as a direct challenge to WP Engine, which had acquired ACF in 2019. Automattic’s new version, Secure Custom Fields, stripped away commercial features, leading WP Engine to label the action a "hostile takeover."
Legal Developments
The dispute quickly transitioned into the legal arena, with WP Engine suing Automattic for alleged anticompetitive behavior. Court documents revealed that Automattic demanded an 8% revenue share from WP Engine or equivalent staffing contributions to regain access to WordPress.org resources. This demand, along with IP blocking and other restrictions, formed the basis of WP Engine’s legal claims.
In December, a federal judge issued a preliminary injunction against Automattic, ordering the company to reverse several actions that had disrupted WP Engine’s operations. Judge Araceli Martínez-Olguín criticized Automattic for marginalizing WP Engine within the WordPress ecosystem and mandated the restoration of WP Engine’s access to WordPress.org resources.
Community Reactions
The suspension of services has sparked frustration within the WordPress community. Developers and users rely on these services for various activities, and the halt is likely to delay projects and disrupt workflows. Mullenweg’s announcement also highlighted the personal toll of the legal battle, as he noted that much of his time is consumed by defending against WP Engine’s legal actions.
Critics of Automattic’s control over WordPress.org argue that it creates a conflict of interest, potentially stifling competition. The forking of the ACF plugin has raised concerns about the future of third-party development within the WordPress ecosystem. WP Engine has framed the conflict as a test of WordPress’s commitment to open-source principles, warning that Mullenweg’s actions could irreparably harm the community.
Looking Ahead
As the legal battle continues, the WordPress community is left grappling with the implications of this conflict. The situation has fueled calls for reforms to WordPress.org’s governance, with some advocating for more independent oversight to ensure fair competition and transparency.
While Automattic maintains that its actions are aimed at enhancing platform security, the scrutiny surrounding its dual role as a commercial entity and steward of open-source WordPress is intensifying. The outcome of this conflict could have lasting effects on the future of WordPress and its community.
