AdvancedCustomFields / AdvancedCustomFields/acf
Field Name case change does not reflect in DB
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
if you change a lowercase letter in the field name to the uppercase letter , it does not create new database row , essentially ignoring the change , leading to your data existing in the ACF tab in wordpress and being shown correctly , but being lost everytime you modify it for some post because the actual field name hasnt changed in the DB .
To Reproduce
- name the field exampleone
- put some value into it for a sample post
- change the field name to exampleOne
- change the value for sample post
- observe your data being empty on every load
Version Information:
- WordPress Version [ Version 6.3.2]
- ACF Version [e.g ACF Free Version 6.2.2]
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 case-change sequence with WordPress 6.3.2 and ACF Free 6.2.2: create exampleone, save a value, rename it to exampleOne, and save again. Then trace the field-name persistence and database update behavior, since the issue names no files or tests. Done means the renamed field retains existing and subsequently saved values on reload, with regression coverage if the project provides a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100