Closed (works as designed)
Project:
CCK Taxonomy Subset
Version:
6.x-1.1
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
2 Jun 2009 at 08:45 UTC
Updated:
11 Sep 2009 at 15:15 UTC
Hello,
If this is not a bug or is something that I've caused due to poor configuration or using too many modules at once, I apologize in advance. However, I'm getting as the only option for all Taxonomy Subset created Display Fields. There should be other options and it was working fine, but it seems that across three different sites (though on the same server), all at once all fields using the module disappeared.
Do you have any idea what could have caused this to happen? It was working fine, then all of the sudden everything went "hidden".
Any ideas?
Thanks in advance.
Comments
Comment #1
lentreprenaute commentedI confirm,
I just install this module but i can't see it in action in display field page (CCK) only one option "hidden" for teaser and node.
Florent
Comment #2
lentreprenaute commentedI noticed that each time that i create a new cck field type "Content Taxonomy Fields" , the field type "Taxonomy Subset" disappear!
Florent
Comment #3
greenc commentedYes, all I get is "hidden" for it. I can't set it as a link or as text in display fields. I hope you can fix this as I really like the concept behind this module, very useful.
Comment #4
lentreprenaute commentedi discovered that it's not necessary "Content Taxonomy Fields"" the problem but if you choose to work with the same vocabulary when you create a other cck field, The field Taxonomy Subset dissapear if a other cck field use the same vocabulary.
Florent
Comment #5
greenc commentedThat's great that you discovered the issue. I hope this can be fixed as there are some situation for which Taxonomy Subset is perfect and other where Content Taxonomy are best. It would be a shame if both can't be deployed at the same time.
Comment #6
greenc commentedThat's great that you discovered the issue. I hope this can be fixed as there are some situation for which Taxonomy Subset is perfect and other where Content Taxonomy are best. It would be a shame if both can't be deployed at the same time.
Comment #7
lentreprenaute commentedGreencrescent,
"Taxonomy Subset is perfect and other where Content Taxonomy are best."
You can use both but you can't working on the same vocabulary
Florent
Comment #8
bwong commentedUnfortunately Content Taxonomy hides what CCK Taxonomy Subset is looking for. I am going to have to look at its internals to figure out whether it is possible to hook into it. For now Florent's observation is correct. You can use them on different taxonomies.