{
  "id": 12051884,
  "title": "Skandal WordPress vs WP Engine: Pengambilalihan Paksa Plugin ACF",
  "url": "https://urgent.news/2026/10/05/skandal-wordpress-vs-wp-engine-pengambilalihan-paksa-plugin-acf",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-05T02:02:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ibramedia/skandal-wordpress-vs-wp-engine-pengambilalihan-paksa-plugin-acf-nbo"
  },
  "original_language": "en",
  "account": "The conflict between WordPress.org and WP Engine reached a peak when WordPress.org unilaterally took over the distribution of the Advanced Custom Fields (ACF) plugin. Through automated update mechanisms, ACF users were redirected to a fork named Secure Custom Fields (SCF). The creation of Secure Custom Fields (SCF) was stated by Matt Mullenweg, the founder of WordPress, to ensure user safety due to WP Engine's perceived loss of access to WordPress.org infrastructure. SCF was introduced as a directly managed alternative by WordPress.org amid the ongoing Automattic vs WP Engine trade dispute. This move raised ethical and trust concerns within the open-source community, questioning the neutrality of the WordPress.org repository. Many developers felt that the unauthorized action against third-party intellectual property undermined the collaborative foundation of open source. The trust in the WordPress ecosystem is now being questioned, especially by developers who rely on the stability chain of software supply for API security and system integration. The forced takeover creates a dangerous precedent. Once the central repository can replace code unilaterally, the stability of distribution is at risk. Users now face the risk of feature incompatibilities or bugs that may arise from the fork created without the involvement of the original developers. Mitigation for developers and website owners who wish to continue using the original ACF version is to manually install it. Avoid automatic updates from the WordPress repository if you need specific features from ACF that may not be present or have changed in SCF. Always monitor the official source from the plugin developer to obtain the version with guaranteed integrity.",
  "summary": "Kronologi Pengambilalihan Plugin ACF oleh WordPress.org Konflik antara WordPress.org dan WP Engine memuncak saat WordPress.org secara sepihak mengambil alih distribusi plugin Advanced Custom Fields (ACF). Melalui mekanisme pembaruan otomatis, pengguna ACF dialihkan ke fork bernama Secure Custom Fields (SCF). Mengapa Secure Custom Fields (SCF) Dibuat? Matt Mullenweg, pendiri WordPress, menyatakan…",
  "key_points": [
    "WordPress.org took over ACF plugin distribution unilaterally.",
    "Secure Custom Fields (SCF) created as WP Engine safety measure.",
    "Ethical concerns raised over unauthorized takeover of third-party code."
  ],
  "editors_take": "The takeover of the ACF plugin by WordPress.org raises concerns about the neutrality of the repository and undermines trust in the WordPress ecosystem, creating a dangerous precedent for unilateral code replacement.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}