#3416 closed defect (bug) (worksforme)
Add plugins data to info v1.2
Reported by: | casiepa | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | API | Keywords: | |
Cc: |
Description
A lot of information exists in different APIs to get information of a plugin. Now that v1.2 is being created, it might be a good idea to unify some of the info.
Starting from e.g. https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]=bbpress I don't see info that is in https://wordpress.org/plugins/wp-json/wp/v2/plugin/213.
3 possibilites:
1) Add the post_id in info/1.2
2) add the missing parts into info/1.2 (like rating, author id, stable_tag, colors, etc)
3) Both 1) and 2)
Change History (1)
Note: See
TracTickets for help on using
tickets.
Most of those things are already available.
post_id
- That's internal and shouldn't be relied upon, all plugins data should be accessed by slug.rating
- Pass therating
field
(It's enabled by default)author id
- We'll refer to everything by user slugstable_tag
- Pass thestable_tag
field.colors
- That's internal directory data that's not needed outside of the directory (and even then, should not be relied upon always being there / in the same format)In general, accessing
/plugins/wp-json/wp/v2/plugin/
should also be avoided for anything, as it's unlikely to remain accessible as it is forever, it's bound to be restricted due to the additional server load which it can cause on non-api-webservers.If there's any useful data that's needed, we can enable that through a
field
statement, but we'll need a use-case for it.I'm going to close this as
worksforme
, but if there's anything specific you need access to, make a specific request ticket for it.(edit: I'll also note that WordPress itself is who the API is designed for, if core doesn't need something, chances are we'll not support it)