Closed (fixed)
Project:
Hierarchical Select
Version:
7.x-3.x-dev
Component:
Code - Taxonomy
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2012 at 19:28 UTC
Updated:
16 May 2013 at 18:40 UTC
I am using hierarchical taxonomy. I have one taxonomy term which has been assigned two parents through relations. The vocabulary is Bar Tab, the term in question is "Both" and the two parent terms are "Food" and "Drinks". When I create content type with term reference field for the Bar Tab Vocabulary, the terms appear in the list as:
None
Food
-Both
DrinksIs there a way to change where in the form the child term appears? I understand why it only shows once instead of twice, but in this case, it would make much more sense to have it appear under the second parent term than the first. I am wondering if there is a way to accomplish this. Any help is greatly appreciated.
Comments
Comment #1
mrweiner commentedSorry, selected content taxonomy instead of just taxonomy.
Comment #2
kars-t commentedDear fellow Drupal enthusiasts,
this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order to remove this issue, I have set this issue to "fixed"
If there is new information, please re-open the issue.