Taxonomies no longer connected to CPTs

  • Resolved relish1227

    (@relish1227)


    3 years, 7 months ago

    My client reached out to say that she couldn’t associate a publication type taxonomy with a publication. I checked and found the following:

    • The taxonomy was not listed under the CPT in the left nav
    • When editing a CPT item, the taxonomy meta box appears on the right side, but is empty — says “No Tags” inside the box
    • If I add an Advance Custom Fields (ACF) taxonomy field, I can select the taxonomy. And I can associate a taxonomy term with a post if I set the ACF field to save and load terms with the record

    I found someone else having this same issue in a closed forum post here from 2019, but I didn’t see a solution. You asked about the REST API setting for the taxonomy. It is set to TRUE for all three taxonomies.

    I did have an old copy of the site on a staging server, the copy being from January. And on that version, the taxonomies are working normally. The staging version is using Version 1.8.2. The problematic install (live) is using Version 1.9.0.

    Any thoughts on what might have changed or what could be causing this? I have not run into this yet on other sites and I use this plugin a lot.

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    While I don’t think it’d affect registration if the taxonomy was already created before the update, I am curious if the taxonomy slug in question is either “types” or “type”

    Both are listed as reserved terms on https://developer.www.ads-software.com/reference/functions/register_taxonomy/#reserved-terms and with CPTUI 1.9.0, we added “types” to our reserved list, alongside “type” which we reserved in a previous version.

    If this is the case, then I’m having to believe we could get the taxonomy slug changed to something else, and still preserve “/types/” or “/type/” in the permalinks for the frontend viewers.

    Thread Starter relish1227

    (@relish1227)

    Thanks for the quick response, Michael.

    Yeah, you know, this site was built back in 2013-14 and when I started using CPTUI I guess I was naming CTPs and taxonomies plural at that time. The taxonomy that I was investigating has this slug: publication-types

    However, there are two other taxonomies and their slugs are “ceu-type” and “artability_video_category” (they were added probably years apart — you can see the last one had the enforced underscore. And I am seeing the same behavior with these ones.

    I just pushed the site to staging and will see what happens when I rename the ones with “type” in them. Okay, nothing changed (still not in the left nav, still says “No tags” in the metabox on the right if I go to add a Publication). I also tried adding a new taxonomy to see if a new one would be added properly, but same situation.

    I wonder what else could be causing this?

    Also, it worries me a bit that any taxonomy with “type” or “types” might not work properly now — is that what you are saying is true with 1.9.0?

    Thanks again.

    • This reply was modified 3 years, 7 months ago by relish1227.
    Thread Starter relish1227

    (@relish1227)

    Okay — I should have done this before responding above: On the staging server I deactivated everything but ACF and CPTUI. And then added them back by 3s or so. And, the plugin that breaks it is User Role Editor Pro.

    I wonder if they, too, are using slugs in some way — and because of that there’s a conflict?

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    the only ones that have been known by use to have issues are when the slugs are explicitly just type or types. Anything else included in the slugs hadn’t been presenting problems, so ceu-type and publication-types would have been fine regarding the reserved slug detail.

    Sounds like something wholly unrelated regarding the conflict with User Role Editor Pro, not something related to slugs.

    Thread Starter relish1227

    (@relish1227)

    Okay, thanks for confirming about the use of “types” and “type.” Whew.

    I will reach out to the URE Pro author to see if they are aware of any possible conflict.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Sounds good.

    Let us know if you need anything else on our side.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Taxonomies no longer connected to CPTs’ is closed to new replies.