• Greetings,

    We’ve run into an odd situation and we’re not sure what’s created it. One and only one custom post type on a site will not “unlock” and allow us to control its capabilities separately. I’m still trying to determine how it’s differently registered than our other post types, and we have marked all of the check boxes under the Unique Post Type Capabilities heading. I’m attempting to include screenshots here. The first shows the Unique Post Type Capabilities box with all check boxes marked. The second one shows that check boxes in the “main editor” that remain disabled.

    Is this something y’all see regularly happen to folks and, if so, can you shed any light on how we might fix it?

    Thank you!
    – Dash

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter David Dashifen Kees

    (@dashifen)

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @dashifen

    Thanks for using PublishPress Capabilities.

    From your screenshots, everything seems already correct. Could you please check if you have already set the custom post type to be public and hierarchical to true?

    Thanks,

    Thread Starter David Dashifen Kees

    (@dashifen)

    Riza,

    Thank you for getting back to me. The post type was public but was not hierarchical. I switched it so that it was hierarchical, but its checkboxes are still disabled. With respect to the screenshots, the second one indicates an entire row of disabled checkboxes for the post type that begins with the letter “A.” In the first screenshot, you can see that we’ve marked every single post type to try and control them via the plugin, but despite this, the “A” post type doesn’t let us do so.

    If you have any advice, it would be most appreciated. We have been trying to fix this on and off for about a year now. For a few more details, we are running 2.13.0 of this plugin WordPress 6.5.5.

    Thanks,
    Dash

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @dashifen Honestly, this behavior is not typical for our plugin. The situation appears to be more complex and may require further troubleshooting.

    Unfortunately, asking for login details is against the guidelines of this forum (www.ads-software.com?Forum Guidelines).

    Our Pro users have the advantage of accessing our private helpdesk, allowing for direct troubleshooting on their sites.

    Considering the complexity of the issue, we recommend upgrading to the Pro version so we can address and troubleshoot it directly on your site.

    If you prefer to keep using the free version, we will need the exact steps on replicating this on fresh WordPress installation.

    Thread Starter David Dashifen Kees

    (@dashifen)

    Honestly, I have no idea why it’s happening in the first place, so I can’t figure out how to recreate it. For now, let’s consider this one a mystery and if I figure anything out, I’ll come back to update this thread in case it helps y’all identify a change on your end or if someone else finds there way here.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @dashifen Sounds good. In the meantime, I will set this discussions to resolved. Feel free to reopen this when you have more information on this issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.