WordPress recently banned WP Engine, a managed WordPress web host, preventing thousands of websites from adding or updating plugins and themes. Technology writer Robert Scoble described the decision as "universally hated in tech," noting that out of hundreds of posts on the subject, nearly none supported Mullenweg’s stance.
Update 09/27/2024
WordPress announced a temporary reprieve for WP Engine customers. Automattic CEO Matt Mullenweg posted on a WordPress forum:
"I’ve heard from WP Engine customers that they are frustrated that WP Engine hasn’t been able to make updates, plugin directory, theme directory, and Openverse work on their sites.
We have lifted the blocks from their servers accessing ours, until October 1, UTC 00:00. Hopefully, this helps them spin up their mirrors of all of our resources that they were using for free while not paying, and making legal threats against us."
What Happened
Matt Mullenweg, co-creator of WordPress, accused WP Engine of infringing on their trademarks and demanded tens of millions of dollars in compensation. The situation escalated on the last day of the recent WordCamp WordPress conference. Mullenweg gave WP Engine until 4:30 PM that day to comply with his demands. Their failure to agree led to public shaming and the subsequent ban of WP Engine.
WordPress.org Bans WP Engine
In a post titled "WP Engine is banned from WordPress.org," Mullenweg announced that WP Engine was cut off from their plugin and theme repository.
"Any WP Engine customers having trouble with their sites should contact WP Engine support and ask them to fix it."
WP Engine posted an incident report on their website, offering a workaround:
"WordPress.org has blocked WP Engine customers from updating and installing plugins and themes via WP Admin. There is currently no impact on the performance, reliability, or security of your site nor does it affect your ability to make updates to your code or content. We are actively developing a remediation for this issue. We will update you as soon as we have a fix.
If you need to install or update a plugin or theme, manual instructions can be found on our support page.
If you have any questions or need assistance, do not hesitate to reach out to our technical support team."
WordPress Core Contributor Sentiment
WordPress core contributors are not pleased with the current situation. An anonymous code contributor posted on Reddit, indicating that the developer community is not siding with Mullenweg.
"WordPress core dev here.
All contributors, Automattic and non-Automattic, are watching closely. This is a community project, and contributors are part of the community. No matter who is listed as project leadership, we’ll continue to be here for the community.
Whether Matt has been accurate doesn’t even come into it for plenty of us. The way this has been done is a significant problem. The community, including us at WordPress core, is not rallying around this action. Everyone I’ve spoken to within the core had no prior notice of this action, raising concerns about more to come. Right now, there’s a deafening silence in contributor-to-contributor communication. We’re trying to regulate our reactions to recent events and avoid kneejerk actions.
Ceasing our contributions would further impact the community, which we definitely don’t want. Even so, if a decision for collective withdrawal of contributions is made, I’d join that action regretfully."
The core contributor also mentioned that Mullenweg has not discussed his plans or course of action with them and confirmed that none of the core contributors have made changes to facilitate his actions.
"It should be crystal clear in Matt’s mind that what’s happening can’t continue. How he chooses to act on that knowledge is anyone’s guess. Unfortunately, his messages so far don’t show signs of anything positive yet."
Social Media Reaction
Posts on X (formerly Twitter) predominantly express disappointment with Mullenweg’s actions and show support for WP Engine.
Technology writer Robert Scoble commented:
"WordPress at war. So sad.
I was one of the first to use WordPress. I didn’t see this coming. I’ve read hundreds of posts about @photomatt’s actions, and almost none are on his side.
Never seen a decision so universally hated in tech. Lots of my old friends are in pain tonight."
Another typical reaction on X:
"This is 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. #WordPress"
Another user posted:
"Gotta say, I’m with WP Engine on this. Not saying they are the ‘good guys,’ but if we all have to pay Automattic for using the word ‘WordPress’ in our marketing, then we’re all in trouble. This sets a dangerous precedent."
Read Mullenweg’s post on WordPress.org for more details.
Read the WP Engine Incident Report for further information.
Featured Image by Shutterstock/Wirestock Creators
