Did WordPress steal ACF in broad daylight… Or what?
In this insight, I will explore the background of the controversy surrounding Advanced Custom Fields (ACF), WP Engine, and the WordPress community, as well as consider what it means for the future.
The controversy surrounding Advanced Custom Fields (ACF) has highlighted the delicate balance between commercial interests and the open-source principles upon which the WordPress platform is built.
What is Advanced Custom Fields (ACF)?
ACF is an indispensable tool for many WordPress developers, as it allows for adding custom fields to posts, pages, and custom post types. This extends WordPress’s core functionality without the need for advanced coding. Its user-friendliness and flexibility have made it a favorite tool in many WordPress projects worldwide.
WP Engine’s acquisition of ACF
In June 2022, WP Engine, a leading provider of managed WordPress hosting, announced its acquisition of several popular plugins from Delicious Brains, including ACF. This news surprised many in the WordPress community. While WP Engine assured continued development and support for these plugins, the acquisition raised concerns among developers and users.
The main fear was that a commercial entity like WP Engine might change ACF’s licensing terms or business model, potentially limiting access or functionality for existing users. There was also uncertainty about whether the plugin’s open-source nature would be preserved and how WP Engine would handle community contributions and future development.
Conflict between WP Engine and Automattic
In September, WordPress founder and Automattic CEO Matt Mullenweg wrote a blog post calling WP Engine “a cancer for WordPress,” stating that despite the absence of a trademark on “WP,” WP Engine uses it in a way that misleads people into thinking they are officially part of WordPress.
In response, WP Engine issued a cease-and-desist letter to Mullenweg, demanding a retraction of his statement. Automattic responded with its own cease-and-desist letter to WP Engine, alleging that WP Engine was misusing the WordPress and WooCommerce names to intentionally imply official affiliation with WordPress.
Automattic then blocked WP Engine’s access to wordpress.org—resulting in numerous websites unable to receive updates for ACF, leaving many sites vulnerable to potential security issues. Small websites became innocent casualties in this conflict.
Following widespread criticism from WordPress users, the block was later lifted.
In early October, WP Engine escalated the situation further by filing a lawsuit against Automattic and Matt Mullenweg in California. WP Engine accused them of abusing power and failing to uphold promises to operate WordPress as an unrestricted open-source project. They argued that Automattic and Mullenweg had failed in their commitment to allow developers freedom to build, run, modify, and distribute the software.
An unexpected turn shakes the WordPress community
Just two days ago, the situation took another unexpected turn. Automattic decided to fork the latest version of ACF from WordPress’s official plugin repository. Forking here involves taking a copy of the code and continuing development independently of the original plugin. The new version was named “Secure Custom Fields” but retained “ACF” in the WordPress menu along with the original ACF logo. Whether this was a deliberate move or a result of haste is unclear.
This action means that all the advanced features previously available in the paid pro version of ACF are now freely accessible through WordPress.org. As a result, two versions of the plugin now exist, which are currently nearly identical in user experience.
WP Engine’s response
Visiting ACF’s official website reveals a message suggesting that WP Engine was caught off guard by Automattic’s move. They’ve had to respond quickly to try to retain as many of their users as possible. It will be interesting to see what specific actions and strategies they will implement moving forward.
Who’s the Villain?
A central dimension in the controversy between WP Engine and Automattic is the question of ethics. Is it justifiable for Automattic to create their own version of Advanced Custom Fields? Open-source licenses like GPL allow anyone to copy, modify, and distribute software, fostering innovation and collaboration. However, it also raises questions about respect for the original development work and the intentions behind the plugin.
Were Automattic’s actions a necessary measure to protect open-source principles, or do they border on a breach of intellectual property? Who bears the responsibility in this situation—WP Engine for potentially shifting ACF’s direction after the acquisition, or Automattic for taking the initiative to create an alternative version? These considerations challenge us to reflect on the balance between community interests and individual rights, and where the line lies between ethical responsibility and self-interest.
What does this mean for the future?
The controversy surrounding Advanced Custom Fields is more than just a dispute between WP Engine and Automattic; it reflects deeper challenges in balancing commercial interests with the values of the open-source community. This situation raises questions about how we, as developers, can navigate a world where core tools can suddenly change direction or ownership.
As a developer, I am following this development closely to ensure my own clients always receive the best solution. Changes in ACF’s availability and functionality could directly impact the projects I work on, so it’s crucial to stay informed and be prepared to adapt. Whether this means choosing between the two versions of ACF or exploring alternative tools, it’s about making decisions that best serve my clients’ interests.
