Why trust Greenbot
WordPress and WP Engine are locked in a fierce showdown after founder Matt Mullenweg pulled the plug on WP Engine’s access to key resources. Announced in a company blog post, the bold move has stirred up the WordPress community, sparking debates over what this means for users, developers, and the broader future of the platform.
“Matt Mullenweg’s unprecedented and unwarranted action interferes with the normal operation of the entire WordPress ecosystem, impacting not just WP Engine and our customers, but all WordPress plugin developers and open source users who depend on WP Engine tools like ACF,” WP Engine said.
Many users felt that they were caught in the crossfire between two corporate entities. “Not being able to do WordPress updates because of the fight is infuriating. For a small nonprofit… this could be costly if we need to migrate our sites to a new host. That money/time should be used for our mission,” Michael Geheren, director of program operations at Emily’s Hope, posted on X.
Not being able to do @WordPress updates because of the @photomatt/@wpengine fight is infuriating.
For a small nonprofit, being caught in the middle of this could be costly if we need to migrate our sites to a new host. That money/time should be used for our mission.
— Michael Geheren (@mgeheren) September 25, 2024
The Root of the Conflict
Mullenweg hasn’t been shy about his disdain for WP Engine, even going as far as labeling them a “cancer” on the WordPress ecosystem. According to him, WP Engine shouldn’t be reaping the benefits of WordPress.org resources unless they’re paying for a trademark license.
For many users, it’s easy to mistake WP Engine for an official arm of WordPress, which Mullenweg argues is part of the problem. WP Engine, he claims, has been riding this wave of confusion to profit.
For clarity, WordPress is an open-source content management system that is freely available and powers roughly 40% of the internet. On the other hand, WP Engine is a plug-and-play hosting service specifically tailored for WordPress users.
Mullenweg also claimed that WP Engine undermines the core principles of WordPress by disabling key features, specifically the revision history that allows users to track changes made to their content.
Conversely, WP Engine contends that it has made significant contributions to the WordPress community, investing millions in sponsorships, educational resources, and open-source projects. The company claims that Mullenweg’s statements are misleading and self-serving.
“WP Engine has been deeply dedicated to advancing the use and adoption of WordPress through innovation and active community involvement,” a representative stated. The company sent a cease-and-decease letter, which explained that its use of the WordPress trademark was covered under fair use.
During Mullenweg’s keynote address at WordCamp US, he allegedly pressured the company into capitulating to Automattic’s financial demands. “This might be the last Word Camp you see WP engine have a booth at,” he said. Reports also indicate that Mullenweg sent a series of messages to WP Engine executives, suggesting that he could have altered his speech to further criticize them if they did not comply.
The Fallout for WP Engine Users
As a result of the ban, WP Engine users are now unable to access vital software updates, leaving their websites vulnerable to security risks. Without the ability to update plugins and themes, businesses relying on WP Engine face the risk of breaking integral functionalities—something that could directly impact revenue and customer trust.
WP Engine has acknowledged the ban and is looking for a workaround, assuring customers that there is currently no impact on the performance or reliability of their sites.
Naturally, both communities are buzzing with concern, with some users considering alternative hosting solutions. The ban not only disrupts WP Engine’s services but also raises questions about the future of collaboration and innovation within the WordPress ecosystem.
