Support content_taxonomy field

it seems to me that content_taxonomy is NOT a multi-dimensional variable
if that's true, then enabling support for it would be pretty straightforward
check the attached patch and laugh

I'll be waiting any negative feedback on this, if a problem comes up (maybe using a special content_taxonomy widget) it will need review regarding multi-dimensional capabilities of content_taxonomy fields

go on with hierarchical_select, it is well supported, you can check the demo site http://sandbox.990.cl/tracker which uses it

the above "widget" hesitation was regarding own content_taxonomy widgets, e.g. "Content Taxonomy Tree" which states "Defines a dynamic tree widget for Content Taxonomy"
I haven't test that one and would prefer to wait for complains regarding its compatibility
moreover, (if it arises with incompatibility issues), it is probable that content_taxonomy bugs (which are several) won't let me work with it and then I would encourage using another kind of supported widget, like hierarchical_select, taxiselect, active_tags, etc, etc

[EDIT]
demo site was moved, it now resides at http://arhak.s4w.biz/tracker, however, if this new URL doesn't work then check the project page to know if it got moved again

and BTW
AHAH is not a problem, it wasn't supported in unstable2 (until I figured it out)
it is an IMPORTANT debugging time warning, since it can be insane trying to find out why the form is bypassing steps
also, there are some known bugs regarding AHAH but normally they won't affect you, since they are related to re-previewing the node, not previewing one time, but consecutive times
read the known bugs at #711094-1: Roadmap

be aware: do not use this approach to enable other kind of CCK modules support, since the multi-dimensional character of the property is a requirement for such a seamlessly integration
otherwise it needs to be reviewed before expanding support
the cost of an improper support expansion would be having wrong diff reports and will require manual cleanup of the diff changes history

committed to HEAD

I have PHP 5.2.9-2
file a new issue with more details regarding the HS settings, the vocabulary type, etc (clarify it was when using it through content_taxonomy, since we also have comment_driven_taxo which supports HS)

content_taxonomy might require a new issue for each widget
re-open this issue if having problems with vanilla content_taxonomy

I was making some changes working with CCK's number support, and changed the "wrapper detection" definition (that name is meaningful to me), which introduced a bug in unstable5 for number with same error msg
PHP Fatal error: Cannot unset string offsets in .../comment_driven_cck.module on line 327
I don't know how content_taxonomy would also fall under that bug, but it shouldn't be present in latest HEAD, please, verify you're up to date

if that error persists, discriminate if it is related to vanilla content_taxonomy or only with HS, file a new issue if it is a widget support matter, otherwise report back here

vanilla content_taxonomy widgets are:
- content_taxonomy_options
- content_taxonomy_autocomplete

therefore widgets to be followed in this issue:
- selects
- radios/checkboxes
- autocompletion

other widgets listed as supported by content_taxonomy and not yet reviewed:
- activeselect
- multiselect
- content_taxonomy_tree (depends on taxonomy_manager)

to request support for the above widgets a new issue might be desirable (unless seamlessly handled by comment_driven_taxo)
for instance, HS got its separated issue #741968: support hs_content_taxonomy widget

for each support request it will be needed to know whether the widget supports:
- hierarchy
- multiple
- tags