#50321 closed enhancement (fixed)
REST API: Add plugin and block directory endpoints
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 5.5 | Priority: | high |
Severity: | normal | Version: | 4.7 |
Component: | REST API | Keywords: | has-patch has-unit-tests has-dev-note |
Focuses: | Cc: |
Description
Gutenberg is introducing REST API endpoints for installing blocks, and activating/deactivating plugins. This is a tracking ticket for handling the core merge of this feature.
Change History (14)
This ticket was mentioned in Slack in #core-restapi by timothybjacobs. View the logs.
5 years ago
This ticket was mentioned in PR #359 on WordPress/wordpress-develop by TimothyBJacobs.
5 years ago
#3
- Keywords has-patch has-unit-tests added
TimothyBJacobs commented on PR #359:
5 years ago
#5
We'll also need a PR to update Gutenberg to use the wp/v2
namespace.
TimothyBJacobs commented on PR #359:
5 years ago
#7
Thoughts on shipping experimental endpoints in core are [mixed](https://make.wordpress.org/core/2020/06/14/shipping-experimental-endpoints-in-core-rest-api-meeting-summary-june-11-2020/) so I'm not really sure about shipping experimental endpoints in general.
For this endpoint in particular, I don't think it needs to be shipped as experimental.
5 years ago
#8
Created a PR for updating the namespaces in Gutenberg: https://github.com/WordPress/gutenberg/pull/23528
I tested out the endpoints, and once I got this PR done , I was able to test out using the block directory — it all worked as expected.
Original Gutenberg PR: https://github.com/WordPress/gutenberg/pull/22454
This also introduces a change in
plugins_api
to not perform a trigger error if this is a json request since we don't want that to break the JSON output.Trac ticket: https://core.trac.wordpress.org/ticket/50321