AdvancedCustomFields / AdvancedCustomFields/acf
Clone fields groups are adding prefixes to the field in seamless or and no seamless.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Clone fields groups are adding prefixes "field_xxxxxxxxxxxx_" to the original field in seamless or and no seamless. Is this expected behaviour? Seems sort of redundant to have it the same on both types as well as having both the array and each individual field labelled as such. There's no way to access the particular field except through the clone field which totally defeats its intended purpose.
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
Reproduce the issue with clone field groups in both seamless and non-seamless modes, then inspect the generated field names and access behavior. Compare the array label and individual field labels to determine whether the prefixes are intentional; done means the expected naming and access behavior is documented or the reported inconsistency is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100