AdvancedCustomFields / AdvancedCustomFields/acf
ACF for Attachment is not editable via REST API but there is an undocumented feature. WP 6.0 ACF 5.12.2
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
If you set the Location Rule as:
Attachment - is equal to - all
You can't edit ACF for attachments (pictures in my case)
but if we add to this rule
or
Post Type - is not equal to - Post
and
Post Type - is not equal to - Page
then it seems to work and we can edit ACF for attachments via REST API
Thank 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
Reproduce the reported behavior in WordPress 6.0 with ACF 5.12.2 using an Attachment location rule and the REST API. Compare it with the workaround that adds the two Post Type exclusions, then identify the relevant ACF REST API and location-rule entry points. Done means attachment fields can be edited through the REST API without the undocumented workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100