WordPress.org bans WP Engine, blocks it from accessing its resources | TechCrunch
WordPress drama went up another notch today after WordPress.org, the free-open source web content hosting software, banned web hosting provider WP Engine from accessing their resources.
In a post on WordPress.org, WordPress co-founder Matt Mullenweg wrote that, pending their legal claims, WP Engine doesn’t have access to the platform’s resources, such as themes and plug-ins.
“WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free,” he said.
“WP Engine is free to offer their hacked up, bastardized simulacra of WordPress’s GPL code to their customers, and they can experience WordPress as WP Engine envisions it, with them getting all of the profits and providing all of the services,” Mullenweg added on the blog.
As a result of this block, sites using WP Engine’s solutions couldn’t install plug-ins or update their themes.
As several WordPress developers and advocates pointed out, WordPress.org blocks WP Engine and also prevents access to security updates for its customers, leaving them vulnerable.
On a status board displaying service status, WP Engine acknowledged this issue and said the company is working on a fix.
“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 impact your ability to make updates to your code or content,” an update from WP Engine read.
The WP Engine vs Automattic/WordPress fight
It’s important to understand that WordPress powers nearly 40% of the websites on the internet through different hosting providers, including Mullenweg’s Automattic and WP Engine. Users can also take the open-source project and run the websites themselves, but a lot of people choose to go with plug-and-play solutions.
The fight began last week when Mullenweg called out WP Engine and said it was “cancer to WordPress.” He also went on to say that the company that has almost half a billion in yearly revenue doesn’t contribute to the WordPress community.
This kicked off a legal battle when, earlier this week, WP Engine sent a cease-and-desist letter to Mullenweg and Automattic, asking them to withdraw their comments. The letter also alleged that Mullenweg threatened WP Engine to pay or face a “‘scorched earth nuclear approach.”
In reply, Automattic sent its own cease-and-desist letter to WP Engine over trademark infringement of WordPress and WooCommerce trademarks just a day later.
Separately, the WordPress Foundation, which is a charity created by Mullenweg to maintain WordPress as an open source project, told TechCrunch that WP Engine has violated its trademarks.
“WP Engine has indeed breached the WordPress Trademark Policy. The Policy states that no one is allowed to use the WordPress trademarks as part of a product, project, service, domain name, or company name. WP Engine has repeatedly violated this policy and the Cease and Desist letter sent to them by Automattic provides examples of some of the many violations,” the foundation said in an email.
The policy was updated yesterday to include an example of WP Engine and calling them out on using WP to confuse customers. Notably, the trademark policy doesn’t cover “WP” as a trademark.
You can contact this reporter at [email protected] or on Singal @ivan.42.
