Forum Replies Created

Viewing 10 replies - 1 through 10 (of 23 total)
  • Author
    Replies
  • in reply to: custom post type capabilities #13782

    meta_gecko
    Participant

    Hi Anh,

    It works fine, but when you add a custom capability then that capability needs to be given to any roles who need it, including administrators.

    This isn’t the responsibility of Meta Box, it’s up to the admin to provide the appropriate permissions to any roles that need it.

    The only thing I’d suggest is that you might want to add some information to the documentation because many people won’t know this otherwise.

    in reply to: custom post type capabilities #13763

    meta_gecko
    Participant

    Just to confirm, adding 'map_meta_cap' => true, solves the problem. Doing so maps all of the primitive capabilities to the custom capability.

    in reply to: custom post type capabilities #13761

    meta_gecko
    Participant

    Hi Anh,

    Thanks for this, however it doesn’t appear to be complete. The custom capability is added, however the capabilities do not appear to be mapped to the core caps required by administrators (or any one else who is granted the capability) to edit published posts etc.

    There should be at least 11 capabilities for the admin role.

    *edit. adding all of the capabilities might not be necessary since they should be inherited.

    It seems that when registering the CPT using MB the mapping of the capabilities are missing:

    'map_meta_cap' => true,

    in reply to: custom post type capabilities #13549

    meta_gecko
    Participant

    Any updates on this request? Unfortunately need to create own types for now because of the capabilities limitation..


    meta_gecko
    Participant

    urgghhh, and the code pasting in this forum doesn’t work properly!

    killing me.

    Here is a screenshot


    meta_gecko
    Participant

    Thanks, I’ve cloned the repo, will test it later this afternoon.


    meta_gecko
    Participant

    Thanks Anh, appreciate it.


    meta_gecko
    Participant

    I’m stumped on this one. I removed that annoyance manually for the moment, but obviously it will keep coming back with every update so I need to find how to fix this permanently please.

    I don’t understand why that check is hardcoded into the field with no options to turn it off from the field parameters?

    Also would like to be able to change the wording with a filter in the cases where it might be useful to display a message.

    Also, why is it printing out on the front end of the site? If you are going to do that then at least wrap the message with a CSS class of its own so that it can either be removed with CSS, JS, and or/styled to look more attractive.

    Thanks, looking forward to a resolution.

    in reply to: Single Image Type Connection returns Array #10566

    meta_gecko
    Participant

    Hi Anh,

    It seems this is a limitation with Themer.

    Currently, only string values will be returned as objects, and arrays are not currently supported by field connections.

    I’m not sure what the solution is, although it would probably save some confusion if this connection was removed and a request sent to Beaver Builder to start adding some notes about the known limitations to their knowledge base (and it would be helpful if you added this to the documentation of the connector plugin too).

    Fortunately I don’t need any too complex with the current site, so I can fudge my way around it.

    I might just decide to dump Themer for the Singular layouts and go back to normal WordPress since the layouts are extremely basic…

    in reply to: 1.5.9 Update fails #10530

    meta_gecko
    Participant

    Hi Anh, that did the trick, thanks 🙂

Viewing 10 replies - 1 through 10 (of 23 total)