WordPress / WordPress/secure-custom-fields
Enable all features that require a filter into Beta Features admin section.
Open
Nobody has claimed this yet.
[Type] Enhancement
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
What
There are a few new features that requires a filter to be enabled, like:
- add_filter( 'acf/settings/enable_datastore', '__return_true' );
- add_filter( 'acf/settings/enable_acf_ai', '__return_true' );
- add_filter( 'acf/settings/enable_schema', '__return_true' );
Those should be enabled by an admin user through the beta features panel, apart from extra filters.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Beta Features admin panel and the registrations for the enable_datastore, enable_acf_ai, and enable_schema filters. Check how existing beta features are exposed, then verify that each listed feature can be enabled by an administrator without adding extra filters. Confirm the panel covers all filter-dependent features named by the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100