WordPress vs. WP Engine: The ACF Plugin Dispute and What It Means for the Community

wp-vs-wp-engine

The WordPress ecosystem has recently been rocked by a high-profile dispute between WordPress.org and WP Engine, centering on the Advanced Custom Fields (ACF) plugin—a widely-used tool that enables developers to create custom content and functionality. The conflict has highlighted deeper tensions within the WordPress community regarding ownership, open-source principles, and control over key components of the platform. Here’s what you need to know about the issue and its potential implications for developers, businesses, and the broader WordPress ecosystem.

The Facts: What Happened?

  1. ACF Plugin at the Center

    The ACF plugin, originally developed by Elliot Condon and later acquired by WP Engine, is a critical tool for many WordPress developers. It allows customization of WordPress beyond the standard post types and fields, enabling tailored functionality for unique website needs.

  2. Ownership and Forking

    After acquiring ACF in 2021, WP Engine integrated it into its suite of tools. However, in October 2024, WordPress.org took control of the ACF plugin repository, citing concerns over how WP Engine was handling updates and licensing. WordPress.org claimed that WP Engine’s approach violated the principles of the General Public License (GPL), which mandates open access and sharing of modifications.

  3. WP Engine’s Fork

    In response, WP Engine forked the ACF plugin, creating a separate version for its customers. This move essentially split ACF into two paths: the WordPress.org-managed version and WP Engine’s proprietary version.

  4. WordPress’s Response

    WordPress.org halted updates to the ACF plugin on its platform, citing WP Engine’s actions as antithetical to the open-source ethos. Matt Mullenweg, co-founder of WordPress, has been vocal about protecting the platform’s open-source nature, framing this as a fight for the integrity of the ecosystem.

Get in touch with us, today

Call, chat with a representative, or fill out the form
202-506-0448
Fill Out Form
Schedule Consult

What’s at Stake?

  1. For Developers

    The forking of ACF could create confusion and challenges for developers who rely on the plugin. They now face a choice: continue using the WordPress.org version, which may diverge in features and updates, or adopt WP Engine’s fork, potentially locking themselves into a proprietary ecosystem.

  2. For WP Engine

    WP Engine’s actions signal an attempt to differentiate itself in the WordPress hosting market by offering exclusive features. However, this move risks alienating developers who value open-source principles and could invite scrutiny from the broader WordPress community.

  3. For WordPress.org

    This dispute underscores WordPress.org’s commitment to maintaining an open and collaborative ecosystem. However, its handling of the situation—effectively seizing control of the plugin repository—has raised concerns about centralization and the limits of its authority over third-party plugins.

A Web Developer’s Perspective

As a Web Development Company with over 15 years of experience exclusively using WordPress, I find this situation troubling on several levels. The ACF plugin is a cornerstone of many custom WordPress builds, and its fragmentation risks undermining the stability and usability of the platform for countless developers and businesses.

WP Engine’s decision to fork the plugin, while within their rights, feels shortsighted. By creating a proprietary version, they risk undermining the trust and goodwill that WordPress has cultivated as an open-source platform. Meanwhile, WordPress.org’s decision to take control of the repository, while rooted in a desire to protect GPL principles, raises questions about the balance of power and how disputes should be handled in a decentralized community.

At its core, this conflict is a reminder of the delicate balance that sustains WordPress: collaboration between independent developers, hosting providers, and users. When one party exerts too much control—whether through proprietary practices or centralized decision-making—it risks destabilizing the ecosystem and eroding the trust that has made WordPress a dominant force on the web.

What Does This Mean for You?

If you’re a business owner or developer relying on ACF, here’s what you can do:

Evaluate Your Needs

Decide whether to stick with the WordPress.org version or adopt WP Engine’s fork. Consider factors like long-term compatibility, support, and alignment with your values as a developer or business owner.

Stay Informed

Follow updates from both WordPress.org and WP Engine. The situation is still evolving, and future developments could impact your choice.

Diversify Your Toolkit

Consider exploring alternative solutions for custom fields and content types. Tools like Meta Box or Pods may offer viable options, depending on your needs.

The ACF dispute is a pivotal moment for the WordPress community, highlighting the ongoing tension between open-source ideals and commercial interests. As developers and businesses, it’s our responsibility to navigate these challenges thoughtfully, ensuring that our choices reflect not just immediate needs but also our commitment to a thriving, collaborative ecosystem. Let’s hope that this conflict ultimately leads to a stronger, more resilient WordPress community.

Let's get Started, Sign Up Today!

Sign Up
<span style="font-size:20px;">by</span> Fevi Yu
by Fevi Yu

SEO Consultant since 2008

Fevi Yu is a seasoned SEO consultant, digital agency founder, and the visionary behind the Basic Website Package—an innovative web and SEO solution crafted for business owners aiming for immediate results. She’s also the creator of the Unlimited WP Maintenance Package, which provides comprehensive WordPress support to enhance website performance and ensure long-term success. This article was written with the assistance of generative AI for enhanced clarity and precision.

Newsletter Sign Up
© 2025 WOWebsites LLC. All Rights Reserved