WordPress Founder Matt Mullenweg Announces Fork of WP Engine's Advanced Custom Fields Plugin

In a significant development within the WordPress ecosystem, founder Matt Mullenweg has announced that WordPress will "fork" the Advanced Custom Fields (ACF) plugin, originally developed by hosting provider WP Engine. This decision marks a critical moment in the ongoing dispute between Mullenweg and WP Engine, highlighting tensions over plugin ownership, user safety, and the ethics of commercial practices in the WordPress community.

A Necessary Step for User Safety

Mullenweg explained that forking ACF into a new plugin called Secure Custom Fields was a necessary move aimed at "removing commercial upsells and fixing a security problem." The goal of this fork is to ensure that users of the plugin have access to a version that prioritizes safety and usability without the complications introduced by commercial interests. This decision reflects a commitment to maintaining the integrity of the WordPress platform and prioritizing user experience.

Reaction from the ACF Team

The response from the ACF team has been swift and critical. They took to social media platform X to express their concerns about the unilateral decision to take away the plugin from its original creators. They described the action as a violation of the fundamental community promise that has governed WordPress for over 21 years. The team argued that this unprecedented move sets a dangerous precedent, urging users to consider the ethical implications of such actions. The ACF team’s response underscores the friction within the WordPress community regarding plugin ownership and control. They emphasized that such an event, where a plugin is forcibly taken from its creators without consent, is a significant breach of trust.

Legal Battles and Background

The dispute between Mullenweg and WP Engine has escalated into legal battles, with accusations and counterclaims being exchanged. Last month, Mullenweg publicly criticized WP Engine, labeling it a "cancer to WordPress" and detailing various grievances, including its lack of support for revision history and the confusion caused by its branding, which might mislead customers into thinking it has official ties to WordPress. The conflict has seen cease-and-desist letters exchanged between both parties, with WP Engine claiming that Mullenweg threatened aggressive legal action unless they paid to license the WordPress trademark. This legal contention culminated in WordPress banning WP Engine from accessing WordPress.org, effectively preventing them from updating the ACF plugin through the official repository. This restriction also means that WP Engine cannot offer automatic updates to address any security vulnerabilities in the plugin. Despite this, WP Engine has provided a workaround for users wishing to continue using ACF, particularly for free users, while Pro users will receive updates through the ACF website.

Moving Forward with Secure Custom Fields

Looking ahead, Mullenweg stated that Secure Custom Fields will be made available as a non-commercial plugin. He extended an invitation to developers who want to contribute to its maintenance and improvement, emphasizing a community-driven approach to its development. This fork serves as an opportunity to ensure that users can benefit from a plugin that aligns with the principles of open-source development and user safety. As the WordPress community watches this unfolding saga, it raises critical questions about the future of plugins, the importance of ethical practices in software development, and the balance of power between creators and commercial entities. The outcome of this dispute may have far-reaching implications for the WordPress ecosystem and its users, reshaping how plugins are developed and maintained in the future.