Download & Extend

Conflict between Primary Term & Content Taxonomy with "Hide default taxonomy fields on the node form" option

Project:Primary Term
Version:6.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (won't fix)

Issue Summary

When Content Taxonomy module is used and I choose "Hide default taxonomy fields on the node form" is selected under "Advanced Settings" in the Content Type Field Mangement Settings for a Content Taxonomy field, NO terms show up in the Primary Term dropdown.

Primary Term dropdown only has terms when I do not select this option in any Content Taxonomy field.

Comments

#1

Title:Issue w/ Content Taxonomy module "Hide default taxonomy fields on the node form" setting» Conflict between Primary Term & Content Taxonomy with "Hide default taxonomy fields on the node form" option
Priority:critical» normal
Status:active» closed (won't fix)

I believe this is due to module weighting -

Primary Term goes looking at the $form, to build the list of Taxonomy Terms.
Context Taxonomy removes terms, meaning if it gets there first, it's going to strip out the items PT depends on being there.

In order to have these co-exist, reweight your modules so Context Taxonomy runs _after_ Primary Term has the chance to form_alter first. Reweighting PT to run earlier isn't feasible, in fact we're likely going to end up as 11 or later, to support #472668: primary_term needs to run after i18ntaxonomy