Map Cap

FAQ

Why aren’t all my custom post types listed on the options page?

There are four requirements for a custom post type to show up in Map Cap’s settings page.

The post type must:

1. be public
2. not be a built-in post type eg. page & post
3. use a custom capability type (not the default capability of post). This is done when registering the Custom Post Type. In the $args array you pass to the register_post_type function, your plugin must have capability_type => set to something other than post.
4. be registered with the map_meta_cap argument set to true – the default is false. Without this parameter set to true, WordPress does not map any meta capabilities.

Force Mapping

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.

Using the Custom Post Type UI plugin?

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.

Where can I report bugs?

Add a new post in the WordPress.org Plugin’s Support Forum.