The Forking of Advanced Custom Fields (ACF) and its Implications

 

The Controversy

In a significant development within the WordPress community, the Advanced Custom Fields (ACF) plugin has been forked. This means that a new, independent version of the plugin has been created, separate from the original ACF developed by Elliot Condon. The forking of ACF was a direct response to the controversial removal of the original plugin from the WordPress.org repository.

The Removal and Subsequent Fork

The original ACF plugin was removed from WordPress.org under circumstances that have been widely criticized. The ACF team maintains that the removal was done without their consent and that the modified version of the plugin that was subsequently made available on WordPress.org introduced potential security vulnerabilities.

In response to these events, the ACF team decided to fork the plugin, creating a new, independent version that they control. This forked version is now available for download from the official ACF website, advancedcustomfields.com.

Impact on the WordPress Community

The forking of ACF has had significant implications for the WordPress community. For users who rely on the plugin for their websites, the situation has created confusion and uncertainty. There are now two versions of ACF available, each with its own advantages and disadvantages.

One of the primary concerns is the potential security risks associated with the modified version of ACF that is available on WordPress.org. The ACF team has warned that this version may contain vulnerabilities that could be exploited by malicious actors.

Another issue is the ongoing dispute between the ACF team and WordPress.org. The controversy has created a rift within the WordPress community, with some users supporting the ACF team and others defending WordPress.org.

The Future of ACF

The future of ACF remains uncertain. It is unclear how the situation will be resolved and whether the two versions of the plugin will eventually be merged.

For users who rely on ACF, it is important to carefully consider the risks and benefits of each version before making a decision. The ACF team has provided guidance on their website to help users choose the appropriate version for their needs.

Options for Users Wanting to Stick with ACF

Given the controversy surrounding the Advanced Custom Fields (ACF) plugin and the availability of two versions, users may be unsure about which path to follow. Here are some options for users who want to stick with ACF:

1. Download the Original ACF from the Official Website

The ACF team has released the original version of the plugin on their official website, advancedcustomfields.com. This version is independent of WordPress.org and is considered to be more secure and reliable. Users can download and install this version directly from the website.

2. Use a Third-Party Repository

Some third-party repositories, such as GitHub, may also host the original version of ACF. Users can search for the plugin on these platforms and download it from there.

3. Contact Your Hosting Provider

If you are using a managed WordPress hosting provider, they may be able to help you install the original version of ACF or provide alternative solutions.

4. Consider Other Custom Field Plugins

If you are unable to obtain or install the original ACF plugin, there are other custom field plugins available that can provide similar functionality. Some popular alternatives include:

• Meta Box: A flexible and powerful custom field plugin with a wide range of features.
• Pods: A versatile plugin that allows you to create custom content types and fields.
• Types: A user-friendly plugin with a drag-and-drop interface for creating custom fields.

It's important to note that while these alternative plugins may offer similar functionality to ACF, they may have different features and interfaces. Users should carefully evaluate their options to find the best plugin for their needs.

By following these steps, users can continue to use Advanced Custom Fields and benefit from its powerful features, even in the face of the ongoing controversy.

Conclusion

The forking of Advanced Custom Fields (ACF) is a significant development with far-reaching implications for the WordPress community. The controversy surrounding the plugin's removal and the subsequent forking have raised important questions about the governance and management of open-source software projects.

As the situation continues to unfold, it is likely that there will be further developments and discussions about the future of ACF.