My personal page for keeping track of what REST API work needs to be done for WordPress 5.0. It’s public so you can easily see it too.
Last updated Tuesday, November 20th.
Here: Next | Blocked | Later| Completed
Elsewhere: Trac REST API Tickets ➚ | GitHub REST API Issues ➚
Next
Priority and should be worked on next.
All REST API issues have been resolved!
Blocked
Blocked in some way.
Nothing blocked right now!
Later
Might be worked on later, if time allows.
- Large ‘include’ argument can cause ‘502 Bad Gateway’ server error
- https://github.com/WordPress/gutenberg/issues/11541
- Needs a pull request from someone with JavaScript chops.
- Provide loading UX when UI is dependent on an API request
- https://github.com/WordPress/gutenberg/issues/6723
- Ready for a pull request from someone with JavaScript chops. It will need design review after completion.
- Present a more specific and descriptive error message when a REST API request fails
- https://github.com/WordPress/gutenberg/issues/10492
- Needs direction on wording for the message, and then a pull request can be worked on.
- Data storage layer should properly handle both context=view and context=edit
- https://github.com/WordPress/gutenberg/issues/11643
- Needs technical discussion before implementation.
- Deleting a new paragraph block triggers a tags request
- Conceptually blocked by the data storage layer issue.
- Increase upper bound allowed on per_page argument
- https://core.trac.wordpress.org/ticket/45140
- Needs memory profiling on the various options before we pick one. Not absolutely necessary for 5.0 though.
- Improved media titles when created from filename
- Patch needs to be verified and include unit tests. As of 10/11, Dave Ryan is working on an updated patch with unit tests.
- Patch needs to be verified and include unit tests. As of 10/11, Dave Ryan is working on an updated patch with unit tests.
- Filter added to ‘page_attributes_dropdown_pages_args’ isn’t applied in Gutenberg, causing page parent relationships to change
- https://github.com/WordPress/gutenberg/issues/9089
- Needs a pull request to introduce an equivalent JavaScript filter.
- Custom Taxonomy: Show in REST, Hide default Gutenberg Panel
- https://github.com/WordPress/gutenberg/issues/6912
- Needs some discussion on whether we want a formal API for this need.
- Use REST API for ajax tag search
- https://core.trac.wordpress.org/ticket/38922
- Doesn’t work for custom taxonomies but the code lives on `trunk` so it doesn’t impact the 5.0 release.
- Create REST API endpoints to lock, release and takeover post edition
- https://core.trac.wordpress.org/ticket/44862
- Proposed implementation is relatively complex. Given the short timeline and the fact that Gutenberg already works with the heartbeat API, this is lower priority.
Completed
#shipped
- Attributes unexpectedly lost in attachment links
- https://core.trac.wordpress.org/ticket/44750
- Fix was committed to WordPress `5.0` branch.
- Declare unfiltered_html capability using JSON Hyper Schema
targetSchema- https://core.trac.wordpress.org/ticket/45014
- Enhancement was committed to the WordPress `5.0` branch.
- Make the “read_private” cap accessible over the REST API
- https://core.trac.wordpress.org/ticket/43701
- Fix was committed to the WordPress `5.0` branch.
- Post Revisions: Adding support for pagination
- Enhancement was committed to the WordPress `5.0` branch.
- Default title and content are not reflected in new editing
- https://github.com/WordPress/gutenberg/issues/8757
- Fix was merged into Gutenberg 4.1.
- Expose permalink_template and generated_slug in the Posts Controller.
- https://core.trac.wordpress.org/ticket/45017
- Enhancement was committed to the WordPress `5.0` branch.
- Add HTTP/1.0 emulation to apiRequest()
- No longer necessary, as this was added to the wordpress/api-fetch package.
- No longer necessary, as this was added to the wordpress/api-fetch package.
- Call wp_debug_mode() to reduce PHP notices that break API responses
- https://github.com/WordPress/gutenberg/issues/10476
- Bug fix was committed to both WordPress 5.0 branch and Gutenberg 4.1.
- Ensure meta wrapper functions do not contain additional logic
- Bug fix was committed to WordPress 5.0 branch.
- Expose theme_supports data on the index or a new, read-only Themes controller
- Feature was committed to the WordPress 5.0 branch.
- Fire an action after items are completely inserted/updated
- Enhancement was committed to the WordPress 5.0 branch.
- Introduce a controller for searching across post types
- https://core.trac.wordpress.org/ticket/39965
- Feature was committed to the WordPress 5.0 branch.
- Saving metadata fails (randomly) if equal value already exists
- Fix was committed to the WordPress 5.0 branch.
- Introduce WP_Block_Type and WP_Block_Type_Registry classes
- Feature was committed to the WordPress 5.0 branch.
- Feature was committed to the WordPress 5.0 branch.
- Page says post updated when it’s a page
- Bug fix was committed to both WordPress 5.0 branch and Gutenberg 4.1.
- Bug fix was committed to both WordPress 5.0 branch and Gutenberg 4.1.
- Support autosaves
- https://core.trac.wordpress.org/ticket/43316
- Feature was committed to the WordPress 5.0 branch.
- Expose Gutenberg Data Format version in the REST API
- https://core.trac.wordpress.org/ticket/43887
- Enhancement was committed to the WordPress 5.0 branch.
- The REST API is not respecting the user’s locale properly.
- Enhancement was committed to the WordPress 5.0 branch.
- Enhancement was committed to the WordPress 5.0 branch.
- Progressively load data into components through pagination
- Enhancement was committed to Gutenberg.
- Add theme support and REST API data for responsive embeds
- https://core.trac.wordpress.org/ticket/45125
- Feature was committed to the WordPress 5.0 branch.
- Introduce WP_REST_Block_Renderer_Controller and WP_REST_Blocks_Controller classes
- Feature was committed to the WordPress 5.0 branch.
- Filter HTML response in oEmbed proxy controller
- Fix was committed to the WordPress 5.0 branch.
- wp_ajax_add_meta() does not allow empty values
- https://core.trac.wordpress.org/ticket/43559
- Enhancement was committed to the WordPress 5.0 branch.
- Include ?_locale=user in JavaScript REST API requests to load user’s locale
- Enhancement was committed to Gutenberg 4.2.
- Enhancement was committed to Gutenberg 4.2.
- Regenerate $fixture_replacements
- Fix was committed to WordPress 5.0 branch.
- 400 bad request trying to autosave empty content
- Fix was committed to Gutenberg 4.3.
- Fix was committed to Gutenberg 4.3.
- GET requests are not localized
- https://github.com/WordPress/gutenberg/issues/11327
- Fix was committed to Gutenberg 4.3.
- Renew nonce to prevent expiration and Updating failed message
- https://github.com/WordPress/gutenberg/issues/9260
- Fix was committed to Gutenberg 4.3.
- Fetch all potential attachments and tags
- https://github.com/WordPress/gutenberg/issues/10873
- Fix was committed to Gutenberg 4.4.
- Draft child pages: parent is removed when an autosave is performed
- https://github.com/WordPress/gutenberg/issues/10753
- Fix was committed to Gutenberg 4.4 and WordPress 5.0 branch.
- register_rest_field() doesn’t work when schema is empty
- https://core.trac.wordpress.org/ticket/45220
- Fix was committed to WordPress 5.0 branch.
- Unrelated meta data gets saved with default value
- https://github.com/WordPress/gutenberg/issues/6505
- Fix was committed to Gutenberg 4.5.
- Meta is not saved to preview
- https://github.com/WordPress/gutenberg/issues/11280
- Fix was committed to Gutenberg 4.5.
- Setting a featured image and clicking Preview does not show the featured image
- Fix was committed to Gutenberg 4.5.