AdvancedCustomFields / AdvancedCustomFields/acf
The ACF API integration issue with attachments
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The ACF API integration is not working properly on attachments. The expected behavior is for the API to return ACF data associated with the attachment and allow saving of ACF data, but it is not functioning as expected.
To Reproduce
Steps to reproduce the behavior:
- Go to the attachment page.
- Access the API endpoint for the attachment.
- Retrieve or update ACF data using the API.
- Notice that the API does not return or save the ACF data as expected.
Expected behavior
The ACF API integration should return the ACF data associated with the attachment and allow saving of ACF data through the API.
Version Information:
- WordPress Version [6.4.3]
- PHP Version [8.2.0]
- ACF Version [ACF PRO 6.2.6.1]
- Browser [Microsoft Edge Version 121.0.2277.106 (Official build) (64-bit)]
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 issue on the listed WordPress, PHP, and ACF versions using an attachment page and the attachment API endpoint. Trace both retrieval and update requests to identify where ACF data is lost. Done means the endpoint returns the attachment's ACF data and saves changes through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100