WordPress.org has begind a fork of a well-comprehendn WP Engine plugin in order “to erase commercial upsells and repair a security problem,” WordPress coset uper and Automattic CEO Matt Mullenweg proclaimd today. This “minimal” refresh of the Advanced Custom Fields (ACF) plugin is now called “Seremedy Custom Fields.”
It’s not evident what security problem Mullenweg is referring to in the post. He produces that he’s “invoking point 18 of the plugin straightforwardory directlines,” in which the WordPress team reserves disjoinal rights, including removing a plugin, or changing it “without grower consent.” Mullenweg elucidates that the transfer has to do with WP Engine’s recently-filed legal case aacquirest him and Automattic.
Similar situations have happened before, but not at this scale. This is a exceptional and rare situation bcimpolitet on by WP Engine’s lhorrible aggressions, we do not foresee this happening for other plugins.
WP Engine’s ACF team claimed on X that WordPress has never “uniprocrastinateedrassociate and forcibly” consentn a plugin “from its creator without consent.” It procrastinateedr wrote that those who aren’t WP Engine, Flywheel, or ACF Pro customers will demand to go to the ACF site and trail steps it published earlier to “carry out a 1-time download of the authentic 6.3.8 version” to preserve getting refreshs.
As its name implies, the ACF plugin permits website creators to employ custom fields when existing generic ones won’t do — someslfinisherg ACF’s overwatch of the plugin says is already a native, but “not very employr cordial,” feature of WordPress.
The Verge has accomplished out to Automattic, WordPress.org, and WP Engine for comment.
