Replace ACF Pro dependency with free SCF - #1
Merged
Merged
Conversation
Secure Custom Fields (SCF) is the free WordPress.org-maintained fork of ACF Pro. It defines ACF_PRO=true and exposes the identical API — blocks, repeater fields, field registration, and all helper functions work without any code changes. - dependencies.php: update messages to point to wordpress.org/plugins/secure-custom-fields - README.md: "Requires ACF Pro" → "Requires SCF (free)" in comparison table and stack line - AGENTS.md: update hard dependency note The brmbh_has_acf_pro() check continues to work as-is since SCF defines ACF_PRO=true. No functional changes — zero paywall blockers remain. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This was referenced Jul 29, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ACF_PRO=trueand exposes the identical API, sobrmbh_has_acf_pro()and all block/field code work without any functional changeswordpress.org/plugins/secure-custom-fieldsinstead of the paid ACF Pro pageWhy
ACF Pro was the only paid dependency in an otherwise fully open-source stack. Anyone cloning the repo hit a paywall before they could run a single block. SCF removes that blocker completely.
What changed
inc/dependencies.phpREADME.mdAGENTS.mdTest plan
wp brmbh scaffoldruns without errors🤖 Generated with Claude Code