ACF is no longer on WordPress.org and now it become SCF, Do you know why?

What Happened?

The conflict began with a controversial takeover of ACF by WordPress.org, which led to the creation of a new plugin called Secure Custom Fields (SCF).This was part of a broader dispute involving Automattic, the parent company of WordPress, and WP Engine, a prominent WordPress hosting provider. Automattic’s legal actions against WP Engine over trademark issues escalated tensions, leading to the decision to fork ACF.

Key Changes

1. Removal from WordPress.org: ACF is no longer available for automatic updates through WordPress.org. Instead, users must manually update to ensure they are using the latest version.
2. Introduction of SCF: The new plugin, SCF, has been introduced as a fork of ACF, aimed at addressing security vulnerabilities while removing commercial upsells found in ACF Pro Download SCF.
3. Security vulnerabilities: The last version of ACF available on WordPress.org before the fork was 6.36, which contained higher security vulnerabilities. Users are now at risk if they do not update to the latest version directly from the ACF website.

Prevention Steps

1. Backup ACF fields
Before making any updates, back up your ACF fields. This precaution helps safeguard your data against potential loss during the transition.

2. How to safely update the ACF Plugin

• For versions 6.37 or 6.38, everything will continue to function normally. However, it’s wise to stay updated for future improvements and security enhancements.
• For Older Versions:
  • Download the latest version of ACF from the official site.
  • Replace your current plugin version by following a detailed guide on installation.

Navigating the transition from ACF to Secure Custom Fields: Frequently Asked Questions (FAQ)

What if You updated the wrong plugin?
Switching from ACF Pro to SCF can cause compatibility issues, particularly with all the fields that are available in SCF Pro eg. repeater, and flexible content.

While existing data remains intact, the repeater field is visible in SCF but does not display on the front end, and new ACF Pro fields cannot be created.

This emphasizes the need for careful plugin updates, as using SCF limits access to ACF Pro’s advanced features.

Is ACF no longer available?
ACF (Advanced Custom Fields) is not completely gone but has been removed from WordPress.org. Instead, it has been forked into a new plugin called Secure Custom Fields (SCF), which is now the version available on WordPress.org.

What to do if i’m using the free ACF plugin?
If you are using the free version of ACF on your website, you should:

• Backup your data: Always back up your ACF fields before making any updates.
• Manually update: Since automatic updates for ACF are no longer available, download the latest version directly from WP Engine if you want to continue using ACF.

Are ACF and SCF the same?
SCF is a fork of ACF created by WordPress to address security issues and remove commercial upsells. While they share some functionality, SCF does not include many of the advanced features found in ACF Pro. In conclusion, we can state that ACF and SCF are not the same thing, although originate from the same company.

Key differences between ACF and SCF

• Ownership: ACF is owned by WP Engine, while SCF is managed by WordPress.org.
• Features: ACF offers advanced features like Repeater Fields and Flexible Content Fields, which SCF lacks.
• Security Focus: SCF was developed with a strong emphasis on security enhancements.
• Commercial Model: ACF has a paid Pro version, whereas SCF is completely free with no upsells.

How to integrate SCF into a website
To integrate SCF into your website:

1. Download SCF: Go to the WordPress plugin repository and download Secure Custom Fields.
2. Install the plugin: Upload it to your WordPress site through the admin panel.
3. Test functionality: Before fully migrating, test SCF in a staging environment to ensure compatibility with your existing setup.
4. Migrate data: If you decide to switch, ensure that all necessary data from ACF is migrated correctly to avoid any loss of functionality.

This transition presents both challenges and opportunities for users of custom fields in WordPress. Evaluating your needs and carefully planning your next steps will be crucial in navigating this change effectively.

If you’re still struggling with the transition from ACF to SCF and aren’t sure what steps to take, we invite you to schedule a free consultation. Our team is here to help you navigate this change and find the best solutions for your needs.