[Resolved] Menu admin is blank if Types is disabled I get it back
This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is whenever the user creates their taxonomy in Types their menu disappears from the frontend and its no longer there in the Appearance -> Menu option.
Solution:
The problem was identified with the use of the slug "output" when creating a taxonomy. What seems to be happening is that 'output' might be an unlisted reserved word for taxonomies.
It should be noted that the problem also occurs when the taxonomy is created using PHP code and when the slug 'output' is assigned.
The user was advised to open a ticket with wordpress core because the issue is not on Toolset side but it's strictly with the wordpress core.
The issue need to be addressed by wordpress directly.
After updating to the latest 3.3.9 Types version, I added a new custom taxonomy and boom! My menu is gone! Gone means is not visible from the admin area (nor the frontend). If I try to add a new item to it, it simply disappears after I hit save.
If I disable Type everything is fine again! Weird enough?
What I did.
All plugins disabled but Type = Same
Default Theme 2020 = Same
Previous version of Type (3.3.8) = Same
Changed php version from 7.3.x to 7.2.x = Same
This is a big problem as I was trying to add new features for a client via Type... :O
Unfortunately, I can't do that since it's live website clients are using. I can try on the dev site but is the one you have access to as well. So yes, as I said, this happened when I first created a new post type + taxonomy on a website that already had CPs. So I wasn't starting from scratch, and this is even weirder if you ask me.
Any confidence in seeing a bug fix/beta version?
Hi Shane is out today and will return tomorrow to continue assisting you here. I took a quick look at the progress from our 2nd tier team and I can see that the issue seems to be directly related to the taxonomy slug "output", and a temporary workaround would be to give the taxonomy a different slug. I can't say with confidence we will be able to offer a patch or hotfix for this quickly, because it could be an issue with WordPress itself - only noticeable with Types active because the taxonomy is registered with Types. Our second tier team will continue investigation and Shane will give you another update tomorrow. Thanks for your patience!
We have gotten a full analysis of the situation here and it is in fact correct that the issue is due to the slug being used. This isn't a bug in our Toolset plugin but a wordpress issue.
What happens is that wordpress seems to be using the slug "output". Any taxonomy created with the slug "output" would cause the issue even if it is a taxonomy created manually using PHP.
If such was the case our plugin would've presented a warning to not use this slug. The recommendation as Christian has advised is to change the slug.
Also it is recommend that you open a ticket directly with the wordpress support as if such is the case they need to add "output" to their reserved words list.
Great to see that you've opened the bug report with wordpress directly. Hopefully they can provide some more information or possibly fix this by adding 'output' to the reserved words.
If there are no further questions on this then you can go ahead and mark this ticket as resolved.
