Active
Project:
Content Taxonomy
Version:
6.x-1.0-beta6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2009 at 20:31 UTC
Updated:
16 Nov 2011 at 12:19 UTC
Hi, I'm not sure if I missed this possible option, but so far there seems to be no way (other than a patch) to unhide the default taxonomy. I'm sure some people don't want it to be hidden.
For example I'm using the default taxonomy as product categories for my online shop and plan to use content taxonomy to reference product categories as accessories.
Comments
Comment #1
account-deletion-needed commentedWhile skimming through the module code I found the following comment:
I didn't find this hide default taxonomy fields option anywhere, so I guess it's planned for a future release?
Comment #2
mh86 commentedThis option has been removed in beta6. I committed a patch, which removed the conflicts between Content Taxonomy and the Taxonomy module. Now it's possible to use Taxonomy Fields with Content Taxonomy Fields with different vocabularies on the same content type. Only Taxonomy Fields with vocabularies, where a content taxonomy field exists, get hidden now.
If you still want to hide a Taxonomy Field, where no Content Taxonomy field with the same vocabulary exists, I recommend you to unselect the content type in the vocabulary settings.
Comment #3
account-deletion-needed commentedThanks, but actually the later is the case, that is using the same vocabulary twice on the same content type. I patched the module so that hook_form_alter() gets commented out and so far it seems to work.
Comment #4
magnus commentedPlease reopen issue if problem still exists.
Comment #5
skylord commentedProblem still exists. Usage case:
1) I have an Ubercart shop with catalog in vocabulary "catalog".
2) I want to build a view in block with accessories for items in some catalog section. I.e. - show some cable on pages of all products in "TV sets" section.
3) So i need mark this cable as accessory for section "TV sets".
4) This module is the best choice for it, but i need to patch it manually and comment out content_taxonomy_form_alter because I need to choose catalog section the product is belonging to and also - mark sections in the same catalog, where this product is considered as accessory.
Please, add some checkbox to alter this behaviour from field settings without patchind the code...
Thanks in advance!
Comment #6
alexbk66- commentedDuplicate #700990: Does not hide core Taxonomy widgets?
Found a fix http://drupal.org/node/700990#comment-4657050
Comment #7
ordually commented#6: Not a duplicate of that issue.
I have the same use case as #5 and #1: my node needs to have core taxonomy and CCK taxonomy field for the same vocabulary.
I commented out the method "content_taxonomy_form_alter" and now it works for my use case. It would be great to have an expose option to handle both behaviors.
Comment #8
farzan commentedI have the same issue as #5. I think hiding/unhiding the core taxonomy should have been optional.
Comment #9
farzan commentedNow I understand the idea behind the auto hiding the core taxonomy widget!
Here is what we -#5 and #7- should do:
- Add 2 cck taxonomy fields; one for core taxonomy, and another one for the additional taxonomy widget.
- For the core taxonomy replacement, check the checkbox labeled "Save values additionally to the core taxonomy system (into the 'term_node' table).". by doing that, the first cck taxonomy completely replaces and behaves as the core taxonomy widget!
Good idea that is not documented well.
Comment #10
skylord commented2 farzan: You suggest a workaround for problem but a complete solution with appropriate checkbox is preferred. Why i have to create additional useless cck field just to deal with this module issue feature/bug????