WordPress.org Bans WP Engine, Blocking Its Resource Access
WordPress.org banned WP Engine from accessing its resources today.
Matt Mullenweg wrote that WP Engine can't access themes or plugins.
"WP Engine wants to control your experience," Mullenweg said.
"They need to run their own login system and update servers."
"Their servers can't access ours for free," he added.
Sites using WP Engine couldn't install plugins or update themes.
Developers noted the block prevents access to security updates.
WP Engine is working on a fix for this issue.
"WordPress.org blocked WP Engine customers from updates," WP Engine said.
"This doesn't impact performance, reliability, or security," they added.
WordPress powers nearly 40% of websites with various providers.
Many users prefer plug-and-play solutions for their websites.
The conflict began when Mullenweg criticized WP Engine last week.
He called the company "cancer to WordPress" due to lack of contributions.
WP Engine then sent a cease-and-desist letter to Mullenweg.
Automattic responded with its own cease-and-desist letter for trademark infringement.
The WordPress Foundation accused WP Engine of breaching trademark policies.
They stated WP Engine used WordPress trademarks improperly.
Automattic's letter cited multiple examples of policy violations.
The trademark policy was updated to highlight WP Engine's misuse.
The policy now addresses WP Engine's confusing use of "WP".
Both parties are currently embroiled in a legal battle.
Matt Mullenweg wrote that WP Engine can't access themes or plugins.
"WP Engine wants to control your experience," Mullenweg said.
"They need to run their own login system and update servers."
"Their servers can't access ours for free," he added.
Sites using WP Engine couldn't install plugins or update themes.
Developers noted the block prevents access to security updates.
WP Engine is working on a fix for this issue.
"WordPress.org blocked WP Engine customers from updates," WP Engine said.
"This doesn't impact performance, reliability, or security," they added.
WordPress powers nearly 40% of websites with various providers.
Many users prefer plug-and-play solutions for their websites.
The conflict began when Mullenweg criticized WP Engine last week.
He called the company "cancer to WordPress" due to lack of contributions.
WP Engine then sent a cease-and-desist letter to Mullenweg.
Automattic responded with its own cease-and-desist letter for trademark infringement.
The WordPress Foundation accused WP Engine of breaching trademark policies.
They stated WP Engine used WordPress trademarks improperly.
Automattic's letter cited multiple examples of policy violations.
The trademark policy was updated to highlight WP Engine's misuse.
The policy now addresses WP Engine's confusing use of "WP".
Both parties are currently embroiled in a legal battle.