WPIntell

Source evidence

Bug: Invalid taxonomy error for existing taxonomy

Ultimate Fields · support · 2015-10-08T05:55:00+00:00

Ultimate Fields plugin evidence original source source API
complaintsentiment
mediumseverity
0.92relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 34 rows with source links

14.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
ranioli unresolved
I’m getting the following error message: UF_Field_Select_Term: Invalid taxonomy! Please check if you’ve spelled the name of the taxonomy correctly and that the taxonomy is already registered! I created a taxonomy for Months, so that I could make the select field multilingual. I created it with ultimate post types and selected my custom post type to attach it to. But when I created the fields for my container using the new taxonomy (after adding terms) and tried to save the container, I got the above mentioned error. I am also getting it when I try to go to taxonomies under ultimate post types. I don’t want to delete the taxonomy. What should I do? My container is also attached to the same post type as the taxonomy. https://wordpress.org/plugins/ultimate-fields/ Hi, The problem was with the order of things. Changing the last line of setup-containers.php in the settings folder to # Do it add_action (‘init’, ‘uf_setup_containers’, 10); seems to fix it. Hi, please incorporate this bug fix in the next update. I updated the plugin and had to make the change once again. If I had not documented it here I would have been searching for the fix all over again.

Comments

2 shown
ranioli 2015-10-08T07:16:00+00:00

Hi, The problem was with the order of things. Changing the last line of setup-containers.php in the settings folder to # Do it add_action (‘init’, ‘uf_setup_containers’, 10); seems to fix it.

ranioli 2016-05-23T20:30:00+00:00

Hi, please incorporate this bug fix in the next update. I updated the plugin and had to make the change once again. If I had not documented it here I would have been searching for the fix all over again.