WordPress.org takes control of WP Engine’s popular plugin

WordPress.org has taken steps to assert control over a plugin developed by WP Engine, following a series of disputes between the two entities. The conflict, which started with criticisms from WordPress founder Matt Mullenweg, centers on trademark infringements and accusations of profiteering by WP Engine. The decision to restrict WP Engine customers from accessing updates and plugins has left many concerned about security vulnerabilities. Both parties have engaged in cease-and-desist actions, escalating tensions that have drawn widespread attention within the WordPress community.

The friction between Automattic, the company behind WordPress, and WP Engine has been intensifying over the past months. Mullenweg’s remarks at WordCamp USA sparked a broader debate, as he labeled WP Engine a “cancer to WordPress” and criticized the company’s lack of contributions to the open-source ecosystem. He accused WP Engine of placing commercial interests ahead of community welfare, despite the company generating substantial revenues from WordPress users.

In response to Mullenweg’s comments, WP Engine issued a legal warning, demanding the retraction of statements made by Mullenweg and Automattic. This led to a standoff, with both sides trading legal threats over the use of WordPress and WooCommerce trademarks. Mullenweg defended his stance by pointing out WP Engine’s continuous violation of the WordPress Trademark Policy, which prohibits using the “WordPress” name in product or service titles.

One of the key flashpoints in this confrontation has been the alleged impact on WP Engine customers. WordPress.org temporarily blocked WP Engine users from updating or installing plugins and themes, which raised concerns about site security and performance. WP Engine acknowledged these issues, assuring customers that efforts were underway to address the problem and restore plugin functionality.

The dispute highlights broader issues about control within the WordPress ecosystem. While WordPress prides itself on being open-source and community-driven, Mullenweg’s actions against WP Engine are being viewed by some as a move toward greater centralization. His criticism of WP Engine’s proprietary systems, which control various aspects of the WordPress experience for their customers, points to a deeper concern about third-party entities monopolizing certain elements of the open-source platform.

Notice an issue?