Repository navigation
Plugins & Theme endpoints #323
Description
Activity
I like the design you've given so far, but I'm not sure on separating POST/PUT. IMO, a better way would be to include an
activekey in the data that gets returned, and allow the client to change this. I'm not sure how updating would work, because you're correct that it is an action, so maybe PUT for that would work. I'll think about this more. :)With implementation, I suspect there'll be a few issues around activating plugins/themes, but otherwise it should be pretty straightforward.
👍 on this. :)
This would potentially allow us to some WPR functionality without requiring a dedicated plugin be installed, big 👍!
Related issue: #107
In the interests of getting something small that could be built on, I'm planning on adding authentication to my work so far, and submitting a pull request for that. Once those basics are in, anyone can build on it.
Does that sound sensible to folks as a way forward?
That sounds great @philipjohn. This could be a big win.
@WP-API/amigos For managing activation, I think we should have a
statusattribute on Plugins and Themes. This will give usactiveandactive-networkTheme management is now WIP as a separate plugin https://github.com/WP-API/wp-api-plugins-themes-endpoints
Is the desire to, at some point, add routes and endpoints for plugins and themes? I.e for checking currently installed plugins/themes, installing and updating?
I'm thinking about a use for this and have the following routes and endpoints in mind...
Route: /plugins
Route: /plugins/[plugin-name]
Route: /themes
Route: /themes/[theme-name]
What do you think?