Control who can publish, edit and delete custom post types on a WordPress site. Silly name, useful code.
Using custom post types on your site?
Install this plugin to control which roles can publish, edit and delete posts of each custom type.
For this plugin to work, your custom post type must meet a number of requirements as outlined in the FAQ.
- Download and unzip the plugin
- Upload the
map-capfolder to the/wp-content/plugins/directory - Activate the plugin through the
Pluginsmenu in WordPress - Navigate to
Map Capunder theSettingsmenu to set capabilities
There are four requirements for a custom post type to show up in Map Cap's settings page.
The post type must:
- be public
- not be a built-in post type eg. page & post
- use a custom capability type (not the default capability of post). This is done when registering the Custom Post Type. In the
$argsarray you pass to theregister_post_typefunction, your plugin must havecapability_type =>set to something other than post. - be registered with the
map_meta_capargument set totrue- the default isfalse. Without this parameter set totrue, WordPress does not map any meta capabilities.
As many custom post types do not set the map_meta_cap to true, Map Cap offers an option to change the value of the map_meta_cap.
For this to work, the plugin must register the post type on the init hook with a priority less than 10,000.
This feature works with the Custom Post Type UI plugin plugin but is not guaranteed to work with any other plugins.
If you are using the Custom Post Type UI plugin, when adding a custom post type, you must click View Advanced Options and change Capability Type to something other than post. For example, for a custom post type of Stories the capability could be story.
You then need select the custom post type under the Force Mapping section of the Map Cap settings page.
Add a new post in the WordPress.org Plugin's Support Forum.
Site administrators can choose the capabilities each role has for each custom post type.
- Changing capabilities for custom posts with "post" capability type no longer allowed
- Option to change the
map_meta_capflag at run-time - When changing a shared capability, a warning is shown
- Readme changes to help resolve common issues.
- Fixing bug where a post without the 'author' feature could not be trashed while having Draft status.
- Initial release.
