WordPress.org forcibly replaces ACF plugin with Secure Custom Fields fork
WordPress.org unilaterally switched users of the Advanced Custom Fields (ACF) plugin to its own Secure Custom Fields fork via automatic updates. Matt Mullenweg cited user security amid the Automattic-WP Engine dispute, sparking debate over the repository's neutrality.
- Automatic updates moved ACF users to the Secure Custom Fields fork
- Mullenweg cited WP Engine's loss of access to WordPress.org infrastructure
- Developers fear damage to repository trust and supply-chain risks
- Manual installation without auto-updates is advised to keep original ACF
Read next
Business