The Automattic CEO started this public battle with WP Engine as he believed WP Engine was violating the WordPress trademarks. Mullenweg even went so far as to call WP Engine a ‘cancer’ to WordPress. Shortly after, more fuel was added to the fire when WordPress announced that it was blocking WP Engine. The hosting provider was thus banned from using its free resources such as plugins and themes. This resulted in a huge backlash from WP Engine customers. These users were left vulnerable due to the discontinuation of crucial security updates from WordPress. The ban was later lifted temporarily until the 1st of October. Automattic also asked WP Engine to pay them 8% of their gross monthly revenue if they want to continue using the WooCommerce and WordPress trademarks. However, WordPress has not accepted these terms by Automattic.

WP Engine had even sent WordPress a cease-and-desist letter demanding that Mullenweg retract his statements about WP Engine. However, Automattic responded with their cease-and-desist letter where they accused WP Engine of infringing on the WooCommerce and WordPress trademarks.

WP Engine Sues Matt Mullenweg: More on this issue

WP Engine has accused Mullenweg of allegedly extorting money from them. As WP Engine sues Matt Mullenweg, the hosting provider also accused the Automattic CEO of abusing his power and being greedy.

The hosting provider is seeking to stop Mullenweg and Automattic from continuing on this tirade against WP Engine and the WordPress community as a whole. The lawsuit has also accused Mullenweg of having an alleged history of blurring the real facts.

Suggested:

Matt Mullenweg Critizes WP Engine at WordCamp US 2024

WordPress Lifts Ban On WP Engine Temporarily

The post WP Engine Sues Matt Mullenweg and Automattic appeared first on Tricky Enough.

In a blog post, Matt Mullenweg, co-founder of WordPress and CEO of Automattic has alleged that WP Engine aims to control the WordPress experience. Sites from WordPress do not get hacked as often as they used to. This is due to WordPress working with hosts to stop ‘vulnerabilities at the network layer. Mullenweg continues by saying that the hosting provider will have to figure out a way to recreate WordPress’ security research by themselves. He also questions the logic of why WordPress has to give free services to WP Engine considering their attacks on WordPress.

The Automattic CEO says WP Engine can proceed with offering customers a bastardized version of WordPress’ GPL code. He ends the blog posts by emphasising that WP Engine is not WordPress.

As WordPress.org blocks WP Engine, loads of WP Engine users have taken to social media to voice their concerns. WP Engine customers have been left vulnerable due to the absence of security updates. The hosting provider has acknowledged this issue and ensured its customers that there is currently no impact regarding security, performance and other concerns. WP Engine has responded to Mullenweg’s claims stating that the Automaacttic CEO interfered with operations within WP Engine.

WordPress.org Blocks WP Engine: Background on this feud

Earlier this week, Mullenweg criticised WP Engine at the WordCamp US 2024 event. After his comments at the event, he later went on to publish a blog post with even more scathing comments. Mullenweg claimed that WP Engine profited off WordPress since 2010 and disabled most of the features that made WordPress what it is.

In his blog post, Mullenweg also called WP Engine a ‘cancer’ to WordPress. Mullenweg stated that WP Engine turned off the revision system. Furthermore, the hosting service has also been alleged to profit from the confusion that exists between WordPress and WP Engine. Mullegnweg has stressed over and over that WordPress is not affiliated with WP Engine by any means.

Suggested:

Matt Mullenweg Critizes WP Engine at WordCamp US 2024.

WordPress 6.7 Update: Final 2024 WordPress Update.

The post WordPress.org Blocks WP Engine appeared first on Tricky Enough.