WordPress.org

Ready to get started?Download WordPress

Forums

Custom Post Type UI
[resolved] Issues with map_meta_cap and 0.8.1beta (5 posts)

  1. Ov3rfly
    Member
    Posted 11 months ago #

    Since 0.8.1beta the setting map_meta_cap is used in CPT UI and set to false as default value (which is documented as default value in the documentation of register_post_type()).

    But setting map_meta_cap to false caused issues with the setting capability_type like 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.

    If the map_meta_cap setting in CPT UI was removed from the register_post_type() call, the issues disappeared, which lead to the conclusion that the default value for map_meta_cap is actually true and not false.

    An annotation in the register_post_type() documentation also points in this direction:

    ... It seems that map_meta_cap needs to be set to true, to make this work.

    Would suggest to use true as default for map_meta_cap in CPT UI or omit the setting from register_post_type() if user has set it to false.

    The use of map_meta_cap might also need more investigation...

    http://wordpress.org/plugins/custom-post-type-ui/

  2. Michael Beckwith
    Member
    Plugin Author

    Posted 11 months ago #

    Ov3rfly, if you could contribute your thoughts over at this issue, that'd be greatly appreciated.

    https://github.com/WebDevStudios/custom-post-type-ui/issues/82

    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.

  3. Ov3rfly
    Member
    Posted 11 months ago #

    As aebs has explained exactly the same above problem already, you could add a link to this thread to github, that should be sufficient.

    More important would be a fix of this serious bug posted by aebs and also found by myself yesterday in the beta version to avoid future annoyance of other developers.

  4. Michael Beckwith
    Member
    Plugin Author

    Posted 11 months ago #

    Just making sure i have enough information to do it right

  5. Michael Beckwith
    Member
    Plugin Author

    Posted 11 months ago #

    Should be all fixed in the latest version. I'm close to 8.1 :D

Reply

You must log in to post.

About this Plugin

About this Topic