wp-api-plugins-themes-endpoints
wp-api-plugins-themes-endpoints copied to clipboard
WP-API
Legacy Feature plugin for Plugin and Theme Endpoints (Superseded by core /themes endpoint)
Not sure if this would be useful/desirable for others?
With the current implementation of plugin gathering we do not have the capabilities to use order, orderby, and search parameters all of which are built into Cores wp-admin view. The...
To explicitly declare the expected format of the Plugin and Theme Resources, they should be first modeled with `get_item_schema()`. The `prepare_item_for_response()` method should use these schemas to determine what data...
There are gaps in test coverage around empty plugin sets, as well as gaps for invalid plugin slugs, and a gap around some of the pagination conditionals. These are currently...
Fixes #17. Currently the permissions do not match what core uses to restric plugin access. This does not account for multisite, which will be added in a separate commit on...
One thing to be aware of is that themes can be installed in subdirectories of `themes`, for instance `wp-content/themes/free/my-awesome-theme`. As such, we'll need to somehow support themes where a `/`...
Currently the schema for themes is empty. I suggest we follow a pattern similar to plugins. We can have all theme headers present along with schema to show if the...
Currently the permissions check looks at `manage_options` this capability does not have to do with plugin access. The correct capability to check is `activate_plugins`. [For Reference](https://codex.wordpress.org/Roles_and_Capabilities#activate_plugins) and [source code reference](https://core.trac.wordpress.org/browser/trunk/src/wp-admin/plugins.php)
…plugins response; initial stab at delete plugin
