The dispute between WordPress founder Matt Mullenweg and internet hosting supplier WP Engine continues, with Mullenweg saying that WordPress is “forking” a plugin developed by WP Engine.
Particularly, Superior Customized Fields — a plugin making it simpler for WordPress customers to customise their edit screens — is being taken out of WP Engine’s palms and up to date as a brand new plugin known as Safe Customized Fields.
Mullenweg wrote that this step was crucial “to take away business upsells and repair a safety downside.”
The Superior Customized Fields staff responded on X, describing this as a scenario the place a plugin “underneath energetic improvement” has been “unilaterally and forcibly taken away from its creator with out consent,” which it mentioned has by no means occurred “within the 21 12 months historical past of WordPress.”
“This important neighborhood promise has been violated, and we ask everybody to contemplate the ethics of such an motion, and the brand new precedent that has been set,” the ACF staff wrote.
Each Mullenweg’s weblog put up and a reply from WordPress declare that related conditions have, the truth is, occurred earlier than, although Mullenweg added, “It is a uncommon and strange scenario introduced on by WP Engine’s authorized assaults, we don’t anticipate this taking place for different plugins.”
Additionally they pointed to WordPress’ plugin pointers, which give WordPress the appropriate to disable or take away any plugin, take away developer entry, or change a plugin “with out developer consent, within the identify of public security.”
Some background: WordPress is a free, open supply content material administration system utilized by many web sites (together with TechCrunch), whereas corporations like WP Engine and Mullenweg’s Automattic provide internet hosting and different business companies on prime.
Final month, Mullenweg revealed a weblog put up criticizing WP Engine as a “most cancers to WordPress.” His criticisms coated every little thing from WP Engine’s lack of help for revision historical past to its investor Silver Lake, however he additionally prompt that its “WP” branding confuses clients, making it sound like the corporate is formally related to WordPress.
Stop-and-desist letters have gone each methods, with WP Engine claiming Mullenweg threatened to take a “scorched earth nuclear strategy” except the corporate paid to license the WordPress trademark.
WordPress banned WP Engine from accessing WordPress.org, briefly lifted the ban, then imposed it once more. This basically prevents WP Engine from updating the plugin via WordPress.org — so it could actually’t provide automated updates to deal with safety points.
WP Engine has, nevertheless, revealed a workaround for customers who wish to replace the plugin and proceed utilizing ACF. (It says the workaround is barely crucial for ACF’s free customers, as professional customers will proceed to obtain updates via the ACF web site.)
Transferring ahead, Mullenweg wrote that Safe Customized Fields might be out there as a non-commercial plugin: “If any builders wish to become involved in sustaining and bettering it, please get in contact.”
