The long-standing feud between WordPress co-founder Matt Mullenweg and WP Engine persists, with Mullenweg accusing the web host of “forking” a WP Engine-developed plugin, sparking fresh controversy in the WordPress community.
Especially, the popular Superior Customized Fields plugin, which simplifies customization of edit screens for WordPress users, is being transferred from WP Engine’s custody and rebranded as Safe Customized Fields, a newly updated plugin.
Muñoz noted that Mullenweg emphasized the importance of this step in removing industrial-scale upsells to rectify a security flaw.
In a unprecedented turn of events, the Superior Customized Fields workforce is grappling with the removal of their plugin from its creator’s control, an unprecedented move in the 21-year history of WordPress.
“The ACF team expressed deep concern over the egregious breach of a crucial commitment, urging everyone to reflect on the ethical implications of this decision and the detrimental precedent it sets.”
Although WordPress co-founder Matt Mullenweg’s blog post and declarations from the company acknowledge comparable circumstances have occurred previously, he notes that “this is a rare and unusual situation brought about by WP Engine’s legal attacks,” adding that they do not expect such events to occur with other plugins.
Additionally, they highlighted a WordPress plugin that grants the platform the authority to disable or remove any plugin, restrict developer access, or modify a plugin “without developer consent, in the name of public safety.”
WordPress is a free, open-source content management system, powering numerous websites, including TechCrunch, while companies like WP Engine and Automattic offer hosting and commercial services on top.
In December, Matt Mullenweg criticized WP Engine as a “cancer to WordPress,” leveling various grievances against the company. His complaints ranged from its failure to support revision history to its backing by investor Silver Lake, but he also argued that WP’s branding confuses customers, implying an official connection between the company and WordPress.
WP Engine has reportedly sent stop-and-desist letters employing various tactics, allegedly prompting Matt Mullenweg to threaten a “scorched earth nuclear strategy” unless the company complies with demands to pay for licensing the WordPress trademark.
WordPress temporarily suspended and subsequently reimposed restrictions on WP Engine’s access to WordPress.org. This effectively blocks WP Engine from automatically updating the plugin through WordPress.org, thereby precluding the ability to proactively address security concerns.
WP Engine, however, provides a solution for customers seeking to replace the plugin and continue using ACF. The workaround is crucial specifically for ACF’s free users, whereas professional customers can receive updates directly from the ACF website.
As Mullenweg looks to the future, he hints at the potential open-sourcing of Safe Customized Fields, stating that the plugin may become available as a non-commercial offering: “Should any developers wish to take on the responsibility of maintaining and enhancing it, please reach out.”
