AdvancedCustomFields / AdvancedCustomFields/acf
Custom ACF field keeping stale data in ACF block
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
In a custom ACF field where we created a relationship field without the fancy select UI, old values are not flushing out when empty values are saved when we use the custom ACF field in an ACF block. The field appears correct. Are custom ACF fields fully compatible with ACF blocks? We seem to be having a stale-data-keeping issue similar to what we have previously seen on classic repeater fields.
Thanks!
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 reproducing the stale-data behavior described for a custom relationship field without the fancy select UI inside an ACF block, saving the field empty and checking whether the old value remains. Compare the behavior with the previously observed classic repeater-field issue; done means empty saves remove the old value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100