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 mandatory “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 “beneath energetic improvement” has been “unilaterally and forcibly taken away from its creator with out consent,” which it stated has by no means occurred “within the 21 yr 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 staff wrote.
Each Mullenweg’s weblog publish and a reply from WordPress declare that comparable conditions have, in reality, 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.”
In addition they pointed to WordPress’ plugin tips, which give WordPress the suitable 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 business providers 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 assist 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” until 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 primarily prevents WP Engine from updating the plugin by way of WordPress.org — so it could’t provide automated updates to handle safety points.
WP Engine has, nonetheless, revealed a workaround for customers who need to replace the plugin and proceed utilizing ACF. (It says the workaround is just mandatory for ACF’s free customers, as professional customers will proceed to obtain updates by way of the ACF web site.)
Shifting ahead, Mullenweg wrote that Safe Customized Fields will probably be obtainable as a non-commercial plugin: “If any builders need to get entangled in sustaining and enhancing it, please get in contact.”
