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 fingers and up to date as a brand new plugin referred to as Safe Customized Fields.
Mullenweg wrote that this step was needed “to take away industrial upsells and repair a safety drawback.”
The Superior Customized Fields workforce responded on X, describing this as a scenario the place a plugin “underneath lively growth” has been “unilaterally and forcibly taken away from its creator with out consent,” which it stated 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 think about the ethics of such an motion, and the brand new precedent that has been set,” the ACF workforce wrote.
Each Mullenweg’s weblog publish and a reply from WordPress declare that comparable conditions have, in truth, 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 occurring for different plugins.”
Additionally they pointed to WordPress’ plugin tips, which give WordPress the correct 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 firms like WP Engine and Mullenweg’s Automattic provide internet hosting and different industrial companies on high.
Final month, Mullenweg revealed a weblog publish criticizing WP Engine as a “most cancers to WordPress.” His criticisms coated every part from WP Engine’s lack of help for revision historical past to its investor Silver Lake, however he additionally steered that its “WP” branding confuses clients, making it sound like the corporate is formally linked to WordPress.
Stop-and-desist letters have gone each methods, with WP Engine claiming Mullenweg threatened to take a “scorched earth nuclear method” 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 by means of WordPress.org — so it might’t provide computerized updates to deal with safety points.
WP Engine has, nonetheless, revealed a workaround for customers who wish to replace the plugin and proceed utilizing ACF. (It says the workaround is simply needed for ACF’s free customers, as professional customers will proceed to obtain updates by means of the ACF web site.)
Transferring ahead, Mullenweg wrote that Safe Customized Fields will likely be out there as a non-commercial plugin: “If any builders wish to get entangled in sustaining and enhancing it, please get in contact.”
