Since 0.8.1beta the setting
map_meta_capis used in CPT UI and set to
falseas default value (which is documented as default value in the documentation of register_post_type()).
falsecaused issues with the setting
capability_typelike e.g. non editable posts of a custom post type post if the post owner is e.g. an editor-role and the current user an admin-role or similar.
map_meta_capsetting in CPT UI was removed from the
register_post_type()call, the issues disappeared, which lead to the conclusion that the default value for
An annotation in the register_post_type() documentation also points in this direction:
… It seems that
map_meta_capneeds to be set to true, to make this work.
Would suggest to use
trueas default for
map_meta_capin CPT UI or omit the setting from
register_post_type()if user has set it to
The use of
map_meta_capmight also need more investigation…
Ov3rfly, if you could contribute your thoughts over at this issue, that’d be greatly appreciated.
I’m not super familiar with this part myself, so I’m kind of relying on those who are to offer suggestions/pointers.
Honestly, this is one that I was originally leaving out, but it got requested so I did some initial work on it.
I’m not against reversing what work I did do, and offer a hook around the post type arguments right before registering, so that those who know what they’re doing with it could add it themselves as necessary.
As aebs has explained exactly the same above problem already, you could add a link to this thread to github, that should be sufficient.
Just making sure i have enough information to do it right
- The topic ‘Issues with map_meta_cap and 0.8.1beta’ is closed to new replies.