Yes, these are set to hierarchical already. And I’m aware that setting these manually isn’t the right approach, but it’s better than the alternative, which is not displaying all the values we need. I will see about getting you access, but thought that I would provide more info as well.
Here are a few examples where what’s in the backend doesn’t match what’s being displayed on the frontend. As you can see, what’s being displayed on the frontend is almost always tied to whether or not there are any posts that have the specific taxonomy value selected.
LOCATION: Frontend
FORM FIELD: Employment Type
Full Time
Internship
Part Time
Seasonal
Temporary
LOCATION: Backend, and the number of posts associated with each.
TAXONOMY: Job Types
Contract (0)
Full Time (61)
Internship (1)
Part Time (1)
Seasonal (2)
Temporary (2)
– AND THE OTHER EXAMPLE –
LOCATION: Frontend
FORM FIELD: Industry
Camping/RVing
Conservation/Wildlife Management
Firearms
Fishing
Food and Beverage
General Outdoors
Golf
Government
Hunting
Mountain Sports
Power Sports
Shooting Sports
Survival
Trapping
Water Sports
LOCATION: Backend, and the number of posts associated with each.
TAXONOMY: Industries
4×4 and Offroad Sports (0)
Agriculture (0)
Camping/RVing (3)
Conservation/Wildlife Management (21)
Firearms (0)
Fishing (4)
Food and Beverage (1)
Forestry (0)
General Outdoors (27)
Golf (2)
Government (5)
Hunting (7)
Mountain Sports (2)
Outdoor Education (0)
Power Sports (0)
Shooting Sports (9)
Survival (0)
Trapping (0)
Water Sports (2)
Winter Sports (0)
Have you confirmed in your testing that all taxonomy terms will appear on a form, even when there are no posts associated with a specific taxonomy term?
Thanks…