• Hi there!

    I just transformed a CPT to a CPTonomy using this plugin. Now when I go to the posttype where the new taxonomy should be enabled, the taxonomies are there, but aren’t selectable. (are disabled) This is the first time this happens to me, usually it works fine.

    It states ‘No All /CPTonomyName/ are selected’ and the html element has the property disabled=’disabled’.

    Does anyone know why this happens? Thanks in advance!

Viewing 7 replies - 1 through 7 (of 7 total)
  • this has happened to me too.
    I reinstalled using the latest wp so it may be a compatability issue with the update?

    This is happening to me as well, WP v4.7.3. Anyone know of a solution, or is this plugin just busted until an update rolls out?

    Still no update on this? I tried all the possible display options (dropdown, autocomplete, checkboxes) and none of them work

    When I select autocomplete it states “There are no CPT selected.”

    Any update is appreciated

    Same here. Are any or all of you also running WooCommerce? I have WP 4.7.5, CPTonomy 1.3.6, WC 3.0.7

    Just testing this plugin for the first time. It’s exactly what I need, just seems to have issues right now. Would love to hear if anyone has narrowed down the problem or found a workaround.

    I had this issue because my taxonomies had hyphens in them instead of underscores.

    When determining if a user has permissions, CPT-onomies uses a regular expression to pull the name of the taxonomy.

    /cpt-onomies/manager.php – line 834
    $taxonomy = preg_replace( '/assign\_cpt\_onomy\_([a-z\_]+)\_terms/i', '\1', $this_cap );

    So your taxonomy slug must only contain lowercase a-z and underscores as per the convention outlined on https://codex.www.ads-software.com/Function_Reference/register_taxonomy.

    Once I updated my custom post type and moved over the posts they were no longer showing up as disabled checkboxes.

    Hope this helps someone!

    Cheers scdan – that solved it for me!

    @scdan, this is great sleuthing. In the months since, my Client moved on from the CPT-as-Tax request, but I went back and verified this anyway, for future reference. One of my four taxonomies was slugified; replacing with underscore solved the problem. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Checkboxes of my CPTonomy disabled’ is closed to new replies.