Advanced Custom Fields (ACF) is a plugin frequently used to create custom fields and content layouts as well as streamline a site’s backend for ease of use, even when complex requirements are involved.
WP Engine’s acquisition of ACF in 2022 and the recent fork of a new version called Secure Custom Fields (SCF) by WordPress contributors, puts users of the plugin in a tough spot that many aren’t really equipped to make a decision on.
At MS Digital Solutions, we don’t take sides in the ongoing debate between WordPress and WP Engine, but we do recognize that our customers are caught in the middle. Our goal is to provide you with information that helps you make the best decision for your business.
Why the ACF vs. SCF Issue Matters
The Advanced Custom Fields plugin has been an indispensable tool for many of our clients, especially small businesses that need custom fields to manage complex content. But with WP Engine now owning ACF, concerns have surfaced around potential changes to the plugin's direction or feature shifts designed to prioritize WP Engine's ecosystem.
In response, the WordPress community developed Secure Custom Fields (SCF), a forked version that remains fully open-source (note, this is only related to the free version of ACF – the features and function of ACF Pro are not included in SCF) and is managed independently by a community of contributors. So now, businesses must decide whether to stick with ACF or make the switch to SCF. If no decision is made, the next update of ACF from the WordPress repository will automatically flow to SCF.
The Challenges Our Clients Face With This Decision
If you’re a client who currently has ACF integrated into your website, we will handle the transition to the ACF version on the WP Engine repository for you. Should you inform us of your preference to switch to SCF, we can do that for you as well. There is no need for you to take on any of the technical work. Keep your focus on your business. But here is a quick guide to how we see the decision.
1. Staying with ACF: The Pros and Cons
For clients who want to avoid the disruption of switching plugins, staying with ACF might seem like the simpler choice. It’s already installed and working, so why change it?
- Pros: ACF has a proven track record of reliability, and under WP Engine’s ownership, it is likely to continue receiving regular updates and support. You won't need to worry about compatibility issues during migration, and the plugin is already integrated into your existing site’s functionality.
- Cons: On the other hand, WP Engine is a for-profit company, which means future updates could prioritize features that align with its business model, possibly introducing premium features or licensing costs. For clients who aren’t using WP Engine’s hosting, this could lead to unnecessary feature bloat or functionality you don’t need, ultimately slowing down site performance.
2. Switching to SCF: The Pros and Cons
For those of you concerned about remaining aligned with WordPress’s open-source principles, switching to SCF may offer peace of mind, but it comes with challenges.
- Pros: SCF promises a fully open-source future, with the focus squarely on compatibility with WordPress and the broader needs of the community, not a specific hosting provider. There’s transparency in development, and for clients who want to avoid potential future licensing fees or restrictions, SCF may provide a more stable, community-driven solution in the long run.
- Cons: Switching isn’t without its risks. Migration between plugins can cause disruptions, especially for businesses that rely heavily on ACF’s features for their site’s day-to-day functionality. SCF is still new, so the community around it isn’t as large, which may mean fewer resources, support, or troubleshooting help compared to ACF. Additionally, there’s the time and effort required to thoroughly test SCF on a staging environment before making any changes to a live site. Additionally, the ability to seamlessly upgrade to the advanced features of ACF Pro is not supported in the new forked version.
A Framework for Decision-Making: What MS Digital Solutions Recommends
Given the complexities, MS Digital Solutions has developed a simple framework to help guide you through this decision-making process. Whether you’re sticking with ACF or considering the switch to SCF, we’ll help you make the best decision based on your business’s unique needs.
1. Prioritize Stability First
If your business relies heavily on ACF’s features and you can’t afford any disruption or downtime, it may be best to stay with ACF, at least for the time being. The plugin is still being actively maintained, and for now, it remains a stable, reliable option. This is especially true if your site is complex, and any changes could cause interruptions to your business.
2. Evaluate Long-Term Costs
For many small businesses, unexpected costs can be a concern. While ACF is currently free to use, WP Engine may introduce premium features or licensing in the future. If cost predictability is important for your business, SCF could offer a more budget-friendly, open-source solution. While migration may involve some upfront time and effort, you could save money in the long run by avoiding any potential future fees.
3. Security and Community Support
For businesses that prioritize security and transparency, SCF’s open-source nature offers greater peace of mind. Its updates and development will always be aligned with WordPress’s community, which means more transparency in security protocols. However, ACF, backed by WP Engine’s resources, may offer more consistent updates in the short term.
4. Test in a Staging Environment
Before making any decisions, we strongly recommend testing SCF in a staging environment. This will allow you to assess how well it integrates with your current site setup and ensure there are no compatibility or performance issues. If SCF can seamlessly replace ACF without significant issues, migration may be worth considering.
Our Path Forward
At MS Digital Solutions, we believe that the customers who have been on ACF for the past 2 years since its acquisition by WP Engine deserve to stay on the plugin that they have relied on for their website. It is entirely possible that the developmental priorities of WP Engine could cause changes in the future. But that is possible with any plugin at any time. So, we believe in an approach that will allow us to cross that bridge when we get to it instead of worrying about problems that may never come to pass.
To that end, we will be downloading and installing the update being offered by WP Engine that will switch the repository of record for future updates to their repository. This is all that should be required to move forward. However, should any client request to make the switch over to the new SCF fork, we will support that as well, without question.