AdvancedCustomFields / AdvancedCustomFields/acf
New REST API implementation does not expose Options Page fields
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
First of all, great news to have ACF fields available in the REST API "natively". This is a major win! 👏🙌
There is, however, one set of fields that are not exposed publicly: The Options Page. We have used the ACF to WP-API plugin to get ACF data out through the REST API until now, where the route for getting options from the options page was /wp-json/wp/v2/acf/options. If possible, /wp-json/wp/v2/options would probably be more in line with the rest of the routes.
This missing route is unfortunately a showstopper for us regarding upgrading to 5.11, because our frontend application is dependent on getting the data from the options page to function properly. 😕
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 tracing the new REST API implementation and compare its available routes with the former /wp-json/wp/v2/acf/options route. Determine how Options Page fields should be exposed, then verify that /wp-json/wp/v2/options returns the required data for the frontend use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100