The court decided in favor of WP Engine in their request for a temporary prohibition of action against Automattic and Matt Mullevega

The Court acknowledged that WP Engine would undergo non -renewable damage if the temporary prohibition was not provided and gave the defendants (Automattic and Mulenweg) 72 hours to return the situation to a state that was on September 20, 2024. Automattic responded to court decision by email to Search Engine Journal:

"Today's decision is a temporary order designed to support the status quo. It has been made without the use of research, our proposal to reject the complaint or the relevant requirements that we will soon submit against WP Engine. We are looking forward to winning the trial, continuing to protect the ecosystem of the open code.

WP Engine has provided such a statement for Search Engine Journal:

"We are grateful that the court has granted our proposal for a temporary prohibition order. This order will return the required stability to the WordPress ecosystem. WP Engine focuses on servicing our partners and clients and cooperation with the community to find ways to ensure an active and prosperous WordPress community.

🚀 The court decided against Mulenweg and Automattic in each argument, giving WP Engine a temporary ban. The solution requires the defendants to restore WP Engine access to WordPress.org, to regain control of the Advanced Custom Fields (ACF) Plugins Directory on WordPress.org and delete a WP Engine client list from Domains.Csv, which is on the WordPressev.

• 📌 The resolution of a trial between WP Engine, Automattic and Mett Mullendweg
• 📌 The impact of a solution on WordPress ecosystem
• 📌 Providing a temporary prohibition of WP Engine