\n<\/p>\n
We\u2019re keenly aware of the impact recent events have had on the WordPress community and ecosystem, and we\u2019re deeply grateful to the many partners and customers who have stood by WP Engine and trust us to serve you in the face of unprecedented and unwarranted attacks and attempts to disrupt our platform.<\/p>\n
WP Engine\u2019s top priority has always been and remains the integrity, security, availability and performance of our tools, and we will continue to take the decisive steps necessary to ensure we can continue to deliver the enterprise-grade experience we\u2019re committed to building.<\/p>\n
Whether as a customer, an agency partner, or a valued member of the WordPress community we\u2019re committed to keeping you updated on the latest developments. With that in mind, we\u2019d like to share the following timeline of our most recent actions and statements:<\/p>\n
On December 10, 2024, the Court issued a ruling granting our request to restore access to and functionality of wordpress.org for WP Engine, its customers and its users.\u00a0<\/p>\n
Specifically, the Court ordered Mullenweg and Automattic to take certain actions, including:\u00a0<\/p>\n
We are grateful that the Court has granted our motion for a preliminary injunction. The order will bring back much-needed stability 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. You can view the Court\u2019s order in full here<\/a>.<\/p>\n On November 14, WP Engine amended and expanded our initial complaint to include antitrust claims brought under laws designed to protect competition and consumers, as well as additional new claims arising from Matt Mullenweg and Automattic\u2019s continued pattern of misconduct.<\/p>\n You can view the amended complaint in full,\u00a0here<\/a>.<\/p>\n On October 18, WP Engine filed a motion for a preliminary injunction, requesting that the court order Matt Mullenweg and Automattic to stop their harmful actions immediately and act to preserve the status quo ante while the case is being litigated.\u00a0<\/p>\n We sought rapid court action to minimize or prevent any further interference with WP Engine\u2019s access to the WordPress community, including WordPress.org and the plugin and theme directory and repository, and to re-establish control over the plugins and extensions we manage as they existed before September 20, 2024. The requested injunction also seeks to provide protection and certainty for WP Engine\u2019s partners, employees, users, and customers, and demand the restoration of any restricted or altered access or operations. You can view the injunction request in full, here<\/a>.<\/p>\n On October 16, WP Engine CEO, Heather Brunner emailed customers to address concerns about recent events and outline the actions we\u2019ve taken to ensure platform stability and security.\u00a0<\/p>\n The letter, which you can read here<\/a>, emphasizes our commitment to protecting customers and supporting the ongoing success of the open-source WordPress community.<\/p>\n On October 12, WordPress.org forcibly took control<\/a> of our Advanced Custom Fields<\/a> (ACF) plugin, marking the first time in WordPress\u2019s 21-year history that a plugin under active development was taken over without consent.<\/p>\n While ACF Pro users remain unaffected, free users are advised to download the latest version of ACF from advancedcustomfields.com<\/a> for secure updates. The ACF team released the following statement<\/a> regarding the takeover:<\/p>\nNovember 14, 2024: Amended legal complaint<\/h3>\n
October 18, 2024: Request for preliminary injunction<\/strong><\/h3>\n
October 16, 2024: Email to customers<\/strong><\/h3>\n
October 12, 2024: ACF takeover<\/strong><\/h3>\n