In a surprising move, WordPress banned WP Engine, a major managed WordPress hosting provider, preventing thousands of websites from adding or updating plugins and themes. Tech journalist Robert Scoble called the decision “universally hated,” and the response from the WordPress community has been overwhelmingly negative, with many criticizing WordPress co-creator Matt Mullenweg for his role in the dispute.

The Backstory

At the heart of this conflict are Matt Mullenweg, co-creator of WordPress, and WP Engine, a company that has built its business around hosting WordPress sites. The tension between these two players came to a head at the recent WordCamp WordPress conference, where Mullenweg publicly accused WP Engine of infringing on WordPress trademarks and demanded substantial compensation, reportedly in the tens of millions of dollars.

In a blog post titled “WP Engine is banned from WordPress.org,” Mullenweg announced the company would no longer have access to WordPress resources, including the plugin and theme repositories, causing immediate chaos for WP Engine customers.

Mullenweg’s stance was blunt: “Any WP Engine customers having trouble with their sites should contact WP Engine support and ask them to fix it.”

In response, WP Engine posted an incident report on its website, offering a workaround and reassuring customers that site performance and security were unaffected. However, users still can’t easily install or update plugins and themes via WP Admin without manually intervening.

WP Engine’s Workaround

WP Engine issued a statement to address the crisis, assuring users that the ban doesn’t affect website performance, security, or their ability to make manual updates to code or content. They provided a guide on how to manually update plugins and themes, directing users to their technical support team for help.

Discontent Among WordPress Contributors

The WordPress core contributor community, which plays a vital role in maintaining the open-source project, has expressed growing frustration. An anonymous core contributor posted on Reddit revealed that the decision blindsided many in the community, including core developers, who were not informed in advance.

In a widely shared post, the contributor voiced concerns over how Mullenweg handled the situation, stating that the contributors are struggling with how to respond. While they have yet to see any positive outcomes, there’s growing discontent and suspicion of more conflicts on the horizon.

The Reddit post emphasized that WordPress is a community-driven project, and contributors feel left out of Mullenweg’s recent actions, which they see as damaging to the spirit of collaboration. They also mentioned that some contributors might consider a temporary halt in their contributions if the situation doesn’t improve.

Backlash on Social Media

On social media, particularly X (formerly Twitter), the response has been overwhelmingly against Mullenweg’s decision. 

Scoble, a notable figure in the tech world, posted, “WordPress at war. So sad.” Many users criticized Mullenweg for what they saw as an abuse of power, with some saying it would set a dangerous precedent if companies like WP Engine had to pay Automattic for using “WordPress” in their marketing materials.

Another typical reaction read: “This is absolutely insane and such a disgusting abuse of power by @photomatt. I have clients using @wpengine and now they can’t easily install plugins or update themes.”

Today in Matt destroys the WordPress community: you can't add plugins directly from the .org repo if you have a WP Engine site. And I can confirm that this is happening.https://t.co/vRd7jliVsM pic.twitter.com/9XGAtXhUoN

— Jacob Martella (@ViewFromTheBox) September 25, 2024

I want to share: https://t.co/CmCwbcxZfD has blocked @wpengine customers from updating and installing plugins and themes via WP Admin—disrupting essential work for #WordPress users, agencies, freelancers, and plugin developers.

Please read: https://t.co/cE45rmvnqW

— Brian Gardner (@bgardner) September 25, 2024

The Bigger Picture: WP Engine vs. Automattic

To understand the significance of this battle, it’s important to know that WordPress powers nearly 40% of all websites online, with hosting services like WP Engine and Automattic being major players in the ecosystem. Automattic, Mullenweg’s company, contributes heavily to the WordPress project, and the tension seems to stem from Mullenweg’s belief that WP Engine is profiteering without giving back to the community in the same way.

Mullenweg previously criticized WP Engine publicly, calling the company a “cancer to WordPress” and accusing them of not contributing enough to the WordPress ecosystem, despite making significant revenue from it. WP Engine responded by sending a cease-and-desist letter, asking Mullenweg to retract his comments. In turn, Automattic also sent a cease-and-desist letter, accusing WP Engine of trademark infringement.

Adding more fuel to the fire, the WordPress Foundation—a charity established by Mullenweg—backed Automattic’s claims, stating that WP Engine had repeatedly violated their trademark policy.

The Fallout

The situation has left many WordPress users and developers in limbo. The ban means WP Engine customers are cut off from key features, such as automatic plugins and theme updates. Security updates are another major concern, as users relying on WP Engine may be left vulnerable if updates aren’t manually implemented.

WP Engine is working on a solution to minimize the impact on its users, but the overall fallout is still unfolding. If a resolution isn’t reached soon, the disruption could extend further, affecting more sites and users within the WordPress ecosystem.

42Works Impact

As a WordPress development company, we at 42Works are also affected by this dispute. WP Engine has been a reliable hosting provider for many of our clients, and this sudden ban complicates updates, plugin management, and security for numerous projects. Our team is closely monitoring the situation and ensuring that our client’s websites remain functional and secure during this upheaval.

How 42Works Can Help

If your business has been impacted by the WordPress-WP Engine conflict, we’re here to assist. At 42Works, we specialize in WordPress development, site maintenance, and providing alternative solutions to ensure your website remains optimized, secure, and up-to-date.

Contact us today to explore your options and let our team help you navigate this challenging period.