Court Orders Automattic to Restore WP Engine’s Access to WordPress.org

Court Orders Automattic to Reinstate WP Engine Access to WordPress.org

A judge in California has mandated that Automattic, alongside its CEO Matt Mullenweg, must reinstate WP Engine’s access to WordPress.org. This repository is owned by Mullenweg and serves as a central hub for themes and plugins.

Details of the Ruling

Judge Araceli Martinez-Olguin stipulated that WP Engine’s access to WordPress.org, including its themes, plugins, and associated subdomains, should be restored to the state it was in on September 20th. This was the date Mullenweg initiated a public dispute with WP Engine, labeling it a detrimental force within the WordPress community.

Following these remarks, WP Engine was promptly barred from accessing WordPress.org.

Lawsuit and Allegations

This preliminary injunction stems from a lawsuit filed by WP Engine, a prominent third-party WordPress hosting provider. The suit alleges Automattic and Mullenweg engaged in extortion and an abuse of power. WP Engine subsequently requested the court to overturn the imposed ban.

Impact on Advanced Custom Fields (ACF)

The ban also prevented WP Engine from accessing and updating its widely-used Advanced Custom Fields (ACF) plugin. After gaining control of ACF, Automattic forked the plugin and rebranded it as Secure Custom Fields (SCF). The court’s decision now requires Automattic to restore WP Engine’s access and control of ACF within WordPress.org.

Context of the WordPress Ecosystem

WordPress currently powers over 40% of all websites. While the platform is open-source and freely available for self-hosting, numerous businesses have emerged to provide hosting services and specialized technical support.

These include Automattic, founded by Mullenweg in 2005 to monetize the project he initially created in 2003, and WP Engine.

Additional Requirements for Automattic

Automattic is also required to remove a publicly accessible list of WP Engine customers. This list was created to showcase the number of customers who had reportedly switched away from WP Engine following Mullenweg’s campaign.

Furthermore, a checkbox on Automattic’s login page, which asks users to confirm they are not affiliated with WP Engine, must also be removed.

Statements from Both Companies

Automattic released a statement indicating their intention to continue pursuing the case. They characterized the ruling as a temporary measure.

“Today’s ruling is a preliminary order designed to maintain the status quo. It was made without the benefit of discovery, our motion to dismiss, or the counterclaims we will be filing against WP Engine shortly,” the statement read.

WP Engine expressed gratitude for the court’s decision, anticipating a return to stability within the WordPress ecosystem.

“We thank the Court for granting our request for a preliminary injunction. The order will bring back much-needed stability and security to the WordPress ecosystem. WP Engine is focused on serving our partners and customers and working with the community to find ways to ensure a vigorous and thriving WordPress community,” a spokesperson stated.

Broader Implications

This situation has sparked debate regarding the open-source nature and overall stability of the WordPress community. Discussions have also centered on defining fair contributions to open-source projects, as Mullenweg had previously criticized WP Engine for perceived insufficient support of the WordPress project.