The ACF vs. SCF drama has unfolded as WordPress decided to fork Advanced Custom Fields (ACF) and release a version called Secure Custom Fields (SCF). The dispute centers around WP Engine, which owns ACF, implementing updates via their own servers instead of WordPress.org, sparking security concerns. In response, WordPress created SCF to keep updates within the official repository and improve security, which they argue is essential for users’ trust in the plugin ecosystem.
Critics, however, see this move as heavy-handed, accusing WordPress of taking control of ACF’s user base and stripping ACF of its commercial upsells. While forking plugins isn’t uncommon, the scale and approach have made this case controversial, with some in the community feeling it reflects poorly on WordPress’s stance toward developer autonomy. WP Engine maintains that its update process was intended for stability and user benefit, while WordPress insists the fork was necessary for security.
The incident highlights ongoing tension between open-source ideals and commercial interests within the WordPress ecosystem, raising questions about the balance between community-driven and corporate-driven development.
Comparing Plugins
Here’s a table comparing the pros and cons of ACF (Advanced Custom Fields) and SCF (Secure Custom Fields) to help illustrate each plugin’s strengths and weaknesses:
| Feature | Advanced Custom Fields | Secure Custom Fields |
|---|---|---|
| Pros | – Established and trusted by developers since 2011. – Offers a wide variety of field types and flexible layouts. – Integrates with ACF Pro for advanced features like repeatable fields, gallery fields, and flexible content layouts. | – Improved security to prevent unauthorized updates and maintain plugin integrity. – Hosted directly on WordPress.org, which allows for transparent updates and reviews. |
| Community Support | – Extensive community support and documentation available due to ACF’s long-standing presence. | – Gained support from WordPress.org for its approach to security and update management. |
| Customization | – Very customizable, especially with ACF Pro, which provides additional features such as custom code snippets and integrations with other plugins. | – Limited to features available in the free version of ACF; excludes advanced ACF Pro functionality. |
| Cons | – WP Engine’s update management (outside WordPress.org) raised concerns over transparency and security. – Lacks some recent WordPress updates for free users on WordPress.org. | – Limited features compared to ACF Pro; may lack advanced field types and repeatable fields. – Limited user and support base since it’s newer and doesn’t offer a paid Pro version. |
Each plugin offers unique strengths: ACF is feature-rich with a strong user base, while SCF is focused on WordPress.org transparency and security. However, users might choose based on their needs for custom field flexibility versus update security.
What if you’re using ACF Pro
If you’re using ACF Pro across all your sites, here are some key points to consider when deciding whether to stay with ACF or explore SCF:
1. Feature Set and Compatibility
- ACF Pro: ACF Pro offers advanced features (like repeater fields, flexible content, and gallery fields) which SCF currently doesn’t support. If these features are critical to your site builds, sticking with ACF Pro is likely the better choice.
- SCF: While SCF is free and secure, it lacks the ACF Pro-exclusive features. SCF may be more suited for simpler implementations where high-end ACF functionality isn’t necessary.
2. Security and Updates
- ACF: ACF Pro updates managed by WP Engine are still secure, but the way they’re handled outside WordPress.org sparked some concern. WP Engine has stated they prioritize stability and security in managing updates, so sticking with ACF Pro remains a secure option, especially for users already comfortable with WP Engine’s practices.
- SCF: SCF emphasizes security, being hosted entirely on WordPress.org and adhering strictly to community-supported update protocols. If security and transparency via WordPress.org are priorities, you may consider transitioning to SCF for simpler sites that don’t rely heavily on ACF Pro’s advanced features.
3. Community and Support
- ACF Pro: Being well-established, ACF Pro has extensive community support, detailed documentation, and established resources. If you’re accustomed to these resources, you’ll find less of this support available with SCF, which is newer and lacks Pro-level documentation and community resources.
Recommendation
If your sites rely heavily on ACF Pro’s advanced capabilities, it’s recommended to continue with ACF Pro, as it maintains stability and feature depth for complex sites.
For simpler sites with basic custom field needs, SCF could be a good choice due to its security transparency on WordPress.org.
Consider experimenting with SCF on a test site to evaluate compatibility before making any changes across multiple live sites.
