A few weeks ago, we broke down the brewing conflict between WordPress and WP Engine—two giants that have historically been partners but now seem more like rivals in a cafeteria food fight. Since then, the battle has only intensified, and the latest twist in this saga? WordPress has “forked” the popular Advanced Custom Fields (ACF) plugin. For those not fluent in developer lingo, a “fork” essentially means splitting off a copy of the original code to create a competing version. Yes, things are getting messier.
Forking ACF: What Happened?
In what feels like a bold power move, WordPress took the open-source ACF code—previously maintained under WP Engine after their 2021 acquisition of Delicious Brains—and launched its own competing version. The official reason? Allegedly, it was to ensure continuity and innovation for ACF users. However, many suspect the fork is more about control: a way for WordPress to wrest back influence from WP Engine, especially over a plugin so critical to the ecosystem.
It’s not just a code fork—it’s a symbolic splitting of loyalties. The open-source community now finds itself in a tricky position. Do developers stick with WP Engine’s version of ACF, which might enjoy better integration with WP Engine’s platform? Or do they switch to the WordPress-controlled fork, which could have tighter compatibility with the core CMS?
Caught in the Crossfire: Millions of Users
This conflict has real consequences for the countless users and developers who rely on ACF to customize WordPress sites. Now, with two competing versions in the wild, confusion reigns. Will plugins built for one version break on the other? Which version will receive the best long-term support? And most importantly, do we really need two ACFS?
Instead of focusing on collaboration or a smooth resolution, WordPress and WP Engine seem intent on proving who can throw the most muck at the other. The stakes, however, extend far beyond their corporate egos—millions of site owners, developers, and agencies are left wondering which side to bet on as these two giants wage their war.
A Food Fight with No Winner (Yet)
This fork feels like the cafeteria brawl we all saw coming, but hoped wouldn’t happen. Like two kids flipping each other’s trays over in a fight for dominance, WordPress and WP Engine’s battle is no longer about principles—it’s about pride. And just like in a food fight, it’s the people sitting quietly at their tables (the users) who are getting hit with stray mashed potatoes.
Meanwhile, site owners have more pressing questions than who wins this battle. They just want their websites to work smoothly, without compatibility issues or political games. But instead of focusing on improving the CMS experience for everyone, WordPress and WP Engine are locked in this messy standoff, leaving users to clean up the fallout.
What’s Next? Stay Tuned for the Aftermath
It’s hard to predict how this story will end. Maybe the forks will coexist peacefully, or maybe one will win out over the other—either through superior features or sheer community pressure. But for now, one thing is clear: this is not the kind of fight anyone asked for.
Our advice to users? Keep an eye on both versions of ACF, test thoroughly before committing to either fork, and make sure your backup plan is ready. In the meantime, we’ll keep monitoring this mess to see whether the food fight continues—or if an adult finally steps in to clean up the cafeteria.
Looking for some additional reading?
1. Advanced Custom Fields Free Fork (or Hostile Takeover?) [VIDEO]
WPTuts dives deep into the ongoing situation surrounding Advanced Custom Fields (ACF) Free and its sudden removal from the WordPress.org repository. He walks you through the key events, including the introduction of “Secure Custom Fields” and the implications of this rebranding.
2. ACF Plugin Forked to ‘Secure Custom Fields’ Plugin
A detailed dive into the block of the ACF plugin, including community reactions and WordPress’ reasoning behind limiting WP Engine’s access.
3. Private Equity and the Soul of WordPress
A discussion on the broader implications of private equity in the WordPress ecosystem, exploring ownership concentration and community governance issues.
4. 21 Years of WordPress Leadership Commentary
This article reflects on the role of Matt Mullenweg, the founder of WordPress, and the controversies surrounding his leadership style amid the ongoing conflict.
Share this post on your social profile:
With more than a decade of agency and in-house experience, Ben is a seasoned veteran of the marketing world and leads YMC’s marketing strategy efforts. From project management to brand marketing, Ben’s depth of experience has helped him develop a well-rounded and detail-oriented approach to solving even the most complex marketing and brand challenges. Most recently, Ben served as the Director of Brand Operations & Strategy for Bonterra – the world’s second largest and fastest growing social good technology company.
Want to get our blogs directly to your inbox?
Enter your email to sign up for our point of view on marketing trends, brand strategy, and sustainable business.
