A court ruled in favor of WP Engine against Automattic and its founder, Matt Mullenweg, in a dispute involving WordPress-related services. The court granted WP Engine a preliminary injunction, requiring Automattic to reverse certain actions they had taken against WP Engine. This decision is critical because it restores WP Engine’s ability to operate and interact within the WordPress ecosystem, ensuring stability for businesses relying on these tools.
Why This Matters to Small Businesses
If your business uses WordPress or the Advanced Custom Fields (ACF) plugin, this ruling is good news. It ensures that WP Engine’s tools and plugins remain functional and accessible, avoiding disruptions to your website or services. The court recognized the importance of maintaining stability in the WordPress ecosystem, which supports over 40% of websites globally, including millions of small businesses.
Key Points of the Ruling:
- Immediate Action Required from Automattic
The court ordered Automattic to:- Restore WP Engine’s access to WordPress.org within 72 hours.
- Revert the control of WP Engine’s ACF plugin to its original state (as of September 20, 2024).
- Remove customer lists and technological blocks that targeted WP Engine.
- Why the Injunction Was Granted
- Irreparable Harm: The judge agreed that WP Engine would face severe harm without this injunction.
- Public Interest: The disruption caused by Automattic’s actions could hurt businesses relying on WordPress and its plugins, including small business websites.
- Balance of Impact: The court found that the injunction imposes minimal burden on Automattic, as it only requires reverting to the previous state of affairs.
- What Happens Next?
- The injunction is temporary, lasting until a final decision is made at trial.
- Automattic plans to fight the decision, but for now, WP Engine has legal support to continue its operations without interference.
What Happened?
WP Engine accused Automattic of actions that unfairly interfered with their ability to operate, including:
- Blocking WP Engine’s access to WordPress.org.
- Taking control of WP Engine’s Advanced Custom Fields (ACF) plugin listing.
- Publishing sensitive customer information on a public tracker.
The court ruled in favor of WP Engine, agreeing that these actions caused irreparable harm and must be undone to prevent further damage. The judge gave Automattic 72 hours to comply with the following directives.
The Court’s Orders
Automattic and Mullenweg must:
- Restore WP Engine’s Access to WordPress.org
WP Engine and its employees must regain full access to WordPress.org accounts and services, which had been blocked. - Reinstate WP Engine’s Control Over ACF Plugin
The Advanced Custom Fields plugin, a tool relied on by over two million websites, must be returned to WP Engine’s control. - Remove Publicly Shared Customer Information
A list of WP Engine customers published on a tracker website and GitHub repository must be deleted. - Undo Technical Blocks
Any technological measures, such as IP blocks or login restrictions targeting WP Engine, must be removed. - Eliminate Anti-WP Engine Login Checkboxes
Automattic added a checkbox at WordPress login requiring users to confirm they were “not affiliated with WP Engine.” This must be removed.
Why the Court Sided with WP Engine
The judge analyzed six key legal areas to make the decision:
- Success on the Merits
WP Engine’s claim of “tortious interference with contractual relations” held strong. Automattic’s arguments to justify their actions were unpersuasive. - Irreparable Harm
The court determined that WP Engine faced severe harm due to the disruptions caused by Automattic. This included loss of access, reputational damage, and customer burden. - Balance of Equities
The court weighed the impact of the injunction on both parties and concluded that requiring Automattic to revert to the previous state caused minimal inconvenience compared to the harm WP Engine faced. - Public Interest
Over 40% of all websites run on WordPress, and two million sites use the ACF plugin. The court recognized that the disruptions caused by this dispute could harm businesses and users globally. - Bond Requirement
Automattic argued that WP Engine should post a $1.6 million bond to cover potential damages if the injunction was unjustified. The judge declined, stating the injunction simply restored the status quo and caused no undue burden. - Scope of the Injunction
The injunction comprehensively addressed WP Engine’s claims, ensuring full restoration of access, tools, and control.
Why This Matters to Small Businesses
If your business relies on WordPress, ACF, or WP Engine’s hosting and tools, this ruling directly impacts you:
- Website Stability: The ruling restores WP Engine’s ability to maintain plugins and provide uninterrupted services.
- Reduced Risk of Disruptions: Actions like restricted access and interference with plugins are halted, ensuring smoother website operations.
- Support for the WordPress Ecosystem: The court emphasized the importance of preserving the open-source WordPress community, which supports businesses like yours.
Automattic’s Response
Automattic issued a statement expressing disagreement with the ruling, emphasizing that it was made without full discovery of facts. They plan to file counterclaims and fight this decision in court.
“Today’s ruling is a preliminary order designed to maintain the status quo… We look forward to prevailing at trial as we continue to protect the open source ecosystem during full-fact discovery and a full review of the merits.”
WP Engine’s Statement
WP Engine welcomed the ruling as a victory for the WordPress ecosystem:
“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.”
FAQ
1. What does this mean for my WordPress website?
If you use WP Engine’s services or the ACF plugin, this ruling ensures they’ll remain stable and accessible, avoiding disruptions caused by the recent disputes.
2. Will there be any changes I need to make?
No changes are required on your end. The ruling focuses on restoring WP Engine’s access and control, which will improve stability for all users.
3. Why is WP Engine important to the WordPress community?
WP Engine provides hosting and tools that enhance the WordPress experience. This decision helps maintain their ability to contribute to and support the broader ecosystem, benefiting businesses like yours.
4. What happens if Automattic wins the trial?
If Automattic ultimately wins, there could be changes to how WP Engine operates. However, for now, stability is ensured until the trial concludes.
5. Should I be concerned about using WordPress?
No. This ruling supports the integrity of the WordPress ecosystem, reinforcing the importance of fair practices. Your reliance on WordPress as a platform remains a solid choice.
Bottom Line:
This ruling is a win for WP Engine and the entire WordPress community, including small businesses. It ensures that the tools and services you depend on will remain accessible and functional during the ongoing legal process. For now, you can continue running your business without worrying about disruptions tied to this dispute.