Closed (won't fix)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Code - Content Taxonomy
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2010 at 07:11 UTC
Updated:
4 Oct 2010 at 08:27 UTC
Comments
Comment #1
wim leersReproduced. Fixed.
This made me curse and laugh at CCK again. It didn't learn much from its mistakes in D5: it's still extremely sucky in D6. Just look at the code I had to add to correct this.
http://drupal.org/cvs?commit=335076
Comment #3
mayerwin commentedHello, I have curiously the same problem, with the latest release (3.1). Works fine with the core "select", but with HS all the terms that have been added in the vocabulary after a certain ID won't get saved (the first ones work).
I have no idea how to debug that.
I tried adding new terms and they are not saved either. Like if the list of possible terms to be saved as default had been frozen at one point.
Same behaviour in all content types that have this field.
Again, the core "select" works, so it seems the problem is not with CCK (but since you first resolved the problem something may have changed in CCK that broke your fix?).
By the way, HS is a great tool! I really appreciate it!
Comment #4
jvieille commentedEven using core taxonomy, default terms are not filled up.
(I use Taxonomy default)
Comment #5
jvieille commentedAny means to set a default value with HS as Taxonomy Default is broken by HS apparently?
http://drupal.org/node/571372
Comment #6
benone commentedHey I use last 3.3 version and default value is not working when set in field options.
When I get to options again its set to none like it was.
I understand it already works in other versions or its only my specific problem ?
my CCK version = "6.x-2.7"
Comment #7
jvieille commentedKeeping on top of my list
Comment #8
wim leersThis isn't a bug, it's a feature request for compatibility with the Taxonomy Defaults module.
I don't have time to add support for this. I welcome a patch, but won't work on it myself.
Comment #9
wim leersClosing due to lack of patch. Feel free to reopen when posting a patch. I won't add this myself.
Comment #10
jvieille commentedMay be this could be more easily solved within HS itself? Just providing default values when creating an HS field as we can already select the taxonomy root?
Just a suggestion for a significant usability improvement.
Comment #11
wim leersSelecting the "Taxonomy root" is a feature provided by Content Taxonomy, not by HS Content Taxonomy. Analogously, this should be implemented in Content Taxonomy.