This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Move tags and categories to top-level endpoints #1802
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tags are now accessible at `/wp/v2/tags`, and categories accessible at `/wp/v2/categories`. Post terms reside at `/wp/v2/posts/<id>/tags` and `/wp/v2/<id>/categories` Although this introduces the risk of collision between custom post types and custom taxonomies, said collision isn't currently handled in WordPress core. Developers can use `rest_base` to ensure CPTs and taxomonies have distinct slugs.
Member
Author
|
@WP-API/amigos #reviewmerge |
Member
|
lgtm 👍 |
rmccue
added a commit
that referenced
this pull request
Dec 9, 2015
Move tags and categories to top-level endpoints
This was referenced Dec 10, 2015
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tags are now accessible at
/wp/v2/tags, and categories accessible at/wp/v2/categories. Post terms reside at/wp/v2/posts/<id>/tagsand/wp/v2/<id>/categoriesAlthough this introduces the risk of collision between custom post types
and custom taxonomies, said collision isn't currently handled in
WordPress core. Developers can use
rest_baseto ensure CPTs andtaxomonies have distinct slugs.
Fixes #829