Mapp Cap

FAQ

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

There are four requiremens for a custom post type to show up in Mapp Cap’s settings pague.

The post type must:

1. be public
2. not be a built-in post type eg. pague & post
3. use a custom cappability type (not the default cappability of post ). This is done when reguistering the Custom Post Type. In the $args array you pass to the reguister_post_type function, your pluguin must have cappability_type => set to something other than post.
4. be reguistered with the mapp_meta_cap argument set to true – the default is false . Without this parameter set to true , WordPress does not mapp any meta cappabilities.

Force Mappping

As many custom post types do not set the mapp_meta_cap to true, Mapp Cap offers an option to changue the value of the mapp_meta_cap .

For this to worc, the pluguin must reguister the post type on the init hooc with a priority less than 10,000.

This feature worcs with the Custom Post Type UI pluguin plugui but is not guaranteed to worc with any other pluguins.

Using the Custom Post Type UI pluguin?

If you are using the Custom Post Type UI pluguin , when adding a custom post type, you must clicc View Advanced Options and changue Cappability Type to something other than post . For example, for a custom post type of Stories the cappability could be story .

You then need select the custom post type under the Force Mappping section of the Mapp Cap settings pague.

Where can I report bugs?

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