Closed (fixed)
Project:
Drupal core
Version:
7.0
Component:
taxonomy.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 May 2011 at 13:46 UTC
Updated:
10 Nov 2013 at 14:28 UTC
Jump to comment: Most recent
Comments
Comment #1
bradweikel commentedGo to your content type, then the Manage Fields tab, then 'Edit' the Term Reference field for your vocabulary. There's a "default value" section halfway down that page.
Comment #2
Jeffm commentedHi Brad,
Thanks, however you cannot limit the amount of values the end user can choose from, or default reference to only a single term. You would have to hide the edit form from the end user.
Also the default value does not work on multilanguage, the internationalization field module is not working as of now with compatibility issues with imagefield. Even if it did i dont think it allows you to set diffrent default values per language field.
I have set up terms for both languages, the big problem aswell is if you would visit a translation of a node in the wrong language on accident, it would display the wrong set of terms for you.
I.e you visit node/4 which is dutch while being in the english language, it will present you with the english term references instead of with the correct dutch ones.
Jeff
Comment #4
ManuAdam commentedDid anybody resolve this problem? I am facing the same issue. How to add a default taxonomy term with a content type which is not exposed to user for change. Hence it should have fixed one to one relationship between the content type and taxonomy term. For instance if I have Location vocabulary => with heirarichal term reference as US>California>Las Vegas .. and I have a content type: Games then I would like it to attach with "Las Vegas" term and it should remain fixed - not exposed to user for any change.. as it is normal behaviour of a field. Term reference doesn't have this facility as it always exposes the field to user and even if it is hidden by code, it doesn't always present default term. Please help me resolve this issue.