AdvancedCustomFields / AdvancedCustomFields/acf
inconsistent htmlentities with acf_form
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I have created a custom text field.
When I enter the value Me & you via the backend and save the post, the value is saved as Me & you in the database.
When I enter the same value in a front-end form created with acf_form(), it is saved as Me & you.
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 at the acf_form() entry point and trace how the custom text field value is prepared before saving. Compare that path with backend post editing, focusing on the different handling of the ampersand. Done means both paths store the entered value as Me & you rather than encoding it inconsistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100