WordPress vs WP Engine

(Updated: October 15, 2024)

Recent tensions have escalated between Matt Mullenweg, founder of The WordPress Foundation and CEO of Automattic, and WP Engine, a separate corporation that offers WordPress hosting and some premium plug-ins. Mullenweg has labeled WP Engine a “cancer” to the open-source community for its perceived exploitation of resources without adequate contribution.

Timeline of Events

1. Mullenweg’s Critique: He called WP Engine out at WordCamp and published a blog post doubling down on his remarks.
2. WP Engine’s Response: Issued a cease-and-desist letter.
3. Automattic’s Counter: Filed its own cease-and-desist letter.
4. Trademark Policy Changes: The WordPress Foundation updated its trademark policies to address WP Engine.
5. Access Restrictions: WP Engine was banned from WordPress.org resources, preventing automatic updates for hosted sites.
6. Community Impact: WP Engine acknowledged the effects of the ban on the WordPress ecosystem.
7. Plugin Control Shift: On October 13th, WordPress.org took control of the Advanced Custom Fields (ACF) plugin, which has been essential to the community since 2011.
8. Forking of ACF: The original ACF plugin remains, while the WordPress.org version is now called Secure Custom Fields (SCF).

Impacts on Users

1. Organizations Hosting on WP Engine
   WP Engine customers must manually update plugins due to the ban on automatic updates. This adds time to routine maintenance and could complicate future updates if the situation worsens.
2. Organizations Using ACF
   With ACF now forked into SCF and ACF, organizations must choose which version to adopt. We have ensured our clients are up-to-date with ACF and have upgraded any free versions to licensed ones, so sites will continue to function smoothly.
3. Organizations Unaffected
   Even if you’re not directly involved, this conflict underscores the importance of having contingency plans and not relying too heavily on any single provider. Our support for open-source software is driven by the flexibility it offers.

Future Considerations

The outcome of this conflict remains uncertain. It could resolve amicably, with both parties prioritizing the community’s interests, or lead to further divides. Possibilities include:

• As a demonstration of their commitment to the community, WP Engine may offer to integrate ACF into the WordPress core.
• The SCF/ACF fork could persist, prompting WP Engine to establish its own version of WordPress, similar to how companies like Samsung have adapted Android.
• A worst-case scenario might echo WordPress’s origins as a fork of b2/cafelog, leading to a proliferation of WordPress offshoots, each serving different community needs.

Regardless of the outcome, the WordPress ecosystem may emerge stronger, even if it operates under different names. This situation highlights the ongoing tension between capitalistic interests and open-source ideals, which must be continually addressed to balance these competing models.

Should You Be Concerned?

If you’re using WordPress without a dedicated support team, stay informed but don’t panic. Our clients can rest assured that we are monitoring developments closely. We have contingency plans in place to ensure uninterrupted website operation. If we identify potential risks, we will inform you and provide options to mitigate disruption.