AdvancedCustomFields / AdvancedCustomFields/acf
ACF 5.8-RC2: Custom field plugin not saving values
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I have a custom field which doesn't save its values unless I first change a default ACF field value. For example I can add and then remove a "!" in a text field and my field value will save successfully.
This started happening post-gutenberg.
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 custom field save failure described in the issue with the Gutenberg editor, comparing saves where a default ACF field is changed with saves where it is untouched. Done means custom field values persist without requiring an unrelated default field change; the payload names no files or tests to guide further investigation.
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
- 25/100