WP Engine and WordPress Dispute: The Implications

A significant dispute between two giants in the web industry has very quickly become public. WP Engine, a popular managed WordPress hosting provider, and WordPress.org, the official home of the WordPress open-source project, have traded blows in the public domain.

Background of the Dispute

The WordPress CEO, Matt Mullenweg, first raised his concerns in a public post titled “WP Engine is not WordPress”. In his post he cited numerous issues including violations of trademark policies, misleading customers that WP Engine is an official WordPress host, disabling core functionality, data integrity concerns, and cost-cutting at users’ expense.

Alongside all these concerns, Mullenweg cited a lack of contributing back to the open-source Content Management System (CMS) whilst simultaneously making vast profits.

Then, four days later, Mullenweg banned WP Engine from using the official WordPress.org resource. WP Engine then responded by issuing a cease-and-desist letter to Automattic [PDF].

This quickly escalating conflict has, as yet, unrealised but potentially far-reaching implications for website owners, publishers, and digital agencies relying on WordPress and WP Engine’s services.

Key Implications for Website Owners and Businesses

There are numerous issues arising from this public spat and they affect website owners and businesses running WordPress websites, as well as digital agencies who use WordPress and WP Engine. Whilst Clever Marketing does not use WP Engine for hosting, we do have a number of SEO clients who host their WordPress websites there.

Potential Service Disruptions

The first and most critical issue is the potential for service disruptions. WP Engine customers may experience issues with their websites due to the company’s loss of access to WordPress.org resources such as:

• Plugin and theme updates could be restricted
• Delays in WordPress core updates might occur
• Increased vulnerability to security threats due to limited access to WordPress.org’s security research

Limited WordPress Experience

Users on the WP Engine platform may have their WordPress experience diminished. For example:

• Some core WordPress features may be disabled or altered

• Access to various WordPress.org resources, including translations and community features, might be restricted

Support and Troubleshooting Challenges

Resolving issues may become more complicated due to WP Engine’s lack of access to WordPress.org resources. Clients experiencing problems are advised to contact WP Engine support directly.

Legal and Business Uncertainties

The escalation to potential legal action raises new concerns:

• WP Engine claims it doesn’t need a license to use the WordPress trademark, citing fair use
• Allegations of extortion and unfair business practices have been made against Automattic’s CEO
• The dispute could potentially impact WP Engine’s operations and service quality

This is an uncomfortable and uncertain time for both belligerents but more so for all users of both WordPress and WP Engine.

Impact on the WordPress Community

This conflict has broader implications for the WordPress ecosystem:

• Trust in both WP Engine and WordPress.org/Automattic may be eroded
• Questions about the balance between commercial interests and open-source principles have been brought to the forefront
• The stability and future direction of the WordPress platform may be called into question

We’ve seen both sides of the arguments, including the original posts and responses, included above. However, talk of forking WordPress, basically cloning out the open-source CMS and building a separate branch, takes us back to the days when Mambo Server split to become the Joomla! CMS.

Recommendations for Clients

Given these developments, anyone using WP Engine should consider the following actions:

1. Evaluate Alternative Hosting Providers: Ensure that you can continue using full WordPress compatibility and feature access by exploring other hosting options.
2. Develop Contingency Plans: Prepare for the possibility of migrating sites if the situation deteriorates further.
3. Enhance Communication: Keep everyone involved with your websites informed about potential risks and limitations associated with using WP Engine.
4. Monitor the Situation: Stay updated on any developments or resolutions between WP Engine and WordPress.org.
5. Assess Legal Implications: Consider the potential impact of the legal dispute on service stability and client websites.
6. Review Platform Choices: Re-evaluate the suitability of WP Engine as a hosting provider given the current uncertainty.

These aren’t nice actions to have to consider but they make commercial sense. Put it this way; what if your website was hacked or, even worse, went down? You need to look at the potential costs to your business and mitigate the risks.

Conclusion

This ongoing conflict underscores the complexity of the WordPress ecosystem and the delicate balance between commercial interests and open-source principles. As a digital agency we’ve had to stay informed about these developments and suggest that website owners and publishers be prepared to adapt strategies to ensure the best possible outcomes for our clients and their website visitors.

The situation remains fluid, and further developments may occur. We recommend closely monitoring official communications from both WP Engine and WordPress.org, and being prepared to take swift action if necessary to protect your clients’ interests and website functionality.

By staying informed and proactive, website owners and publishers can navigate this challenging situation and continue to provide value and stability to their users.

If you need advice or assistance with migrating your WP Engine to another hosting provider, call us on 01276 402 381 for an immediate chat.