Incompatible with Content Taxonomy

I am using 3 content_taxonomy fields with 'select' widgets.
One of them should be the HS 2 supported ( Catergory taxonomy tree, 4 levels deep),
the others are only 1 level taxonomy trees (language, subtitle) select lists.
I also use some autocomplete content_taxonomy fields (artist, city, country etc.).

In my last Test (running HS 2) i created a new content type and added the content_taxonomy field ( in my case the field category).
Using add node shows up the content_taxonomy field as HS 2, with all features.
Now i added some 'pure' cck fields and they show up too.
But if i'm adding one more cck field which comes along with the content_taxonomy kills the HS 2 dynamic select list
and downgrades it to a 'normels' select widget. It doesent matter if it's a autoselect content taxonomy field or a content taxonomy select list widget.

For me it looks like that more than one content_taxonomy field in the edit node form, disables HS 2 and the HS 1 dev Version.

Thanx for the fast response!

I set up two fresh sandbox installtions.
One with Drupal 5.3 (my production site version) and one with Drupal 5.5.
Both with the following modules:

CCK Version: 5.x-1.6-1
Hierarchical Select: Version: 5.x-2.0-beta2
Content Taxonomy Version: 5.x-1.x-dev
JQuery Update Version: 5.x-1.0
JQuery Interface Library Version: 5.x-1.0

I configured the page content type with:
- 1 Taxonomy field with HS2 enabled, Hierachy: Multiple, Multiple select, Required, 4 levels deep
HS Coniguration: Save term lineage, allow user choose from any level

- 1 Taxonomy field without HS2, autocomplete, Hierachy: Single, Free tagging, Required

HS2 dynamic select shows up in both Drupal installations, but when i select the terms, the following happend:

Bug1 (select boxes):
Level1: Only Level 1 Terms showing up - OK
Level2: All Terms from any depper levels showing up in the select list - same on level3 but without the level2 terms.

Bug2 (selection box) :
If a 4 level deep term is added the 'all selctions' box in the node edit form looks like this:
Level1 > Level4
Level1 > Level3 > Level4
Level1 > Level2 > Level3
Level1 > Level2 > Level3 > Level4
After submitting the node the terms appears correctly.

Both bugs look like a known content taxonomy problem.
The default content taxonomy release also shows every term in every cck field after publishing the node.
That means if you have eg. 4 content taxonomy fields in a content type, every term will show up 4 times in the submitted node. At the end you will have 12 terms (4x4).

There is a patch to fix this http://drupal.org/node/168702 which i am also using on my production site (patch applied manually + also removed hardcoded 'br' tag).

So, this patch fixes both above-named bugs bugs on my sandbox installations,
but not on my real production site which is more than strange.

I will look into it and post if i made any configuration mistake or if another module cause this.

In my opinion HS2 works fine.

Thanx Wim for patching!

Ok, i posted to early that everything is looking fine.
I just tried to fix aboved-mentioned taxonomy erros on my production site than i found out that it already works on the first content type, but only there.

I have to explain that i have none of the content types associated with any vocabularies.
So i first thought this is the mistake. But it wasn't.

Good. So i tried to reproduce the error on my sandbox installations (same setup like a post before) and after a while i figured out:

1. Associating the vocabularies to the content type result in double appearance of the fields,
but at least HS2 shows up ( I could see that on my prdouction site, because i themed the input forms with phptemplate).

2. No associating shows HS2 only on the first content type (in alphabetically order).

The worst thing is that only the second version works for my production site and also only on the first content type.

I could make a backup of my site and disable module after module or remove field after field to find out what else HS2 breaks, but that will take some while.

Maybe my explanation is good enough that you have any clue whats going wrong.

THX for the support!

Sorry that my writing is confusing (bad english?, too much coffee?).
I wanted to give you a step by step description what i already tried to isolate the error.
Thought it would help you - Probably it was to much text ;)

Summary:

The goal is to use HS2 with the same vocabulary on ten content typs.

I set up one Vocabulary with some terms, HS2 enabeld.
First content type shows HS2.
Second content typ only shows the default content taxonomy select list, not the HS2 dynamic select list.

The question is:
Can i use HS2 with the same vocabulary on different content typs?

Sorry that i can't stop bother you, but Step 5 just doesn't work.

I can assign the field to every content type i want, but only the first content type will show a HS2 list.

I tried it on 2 different 'fesh' installtions on 2 Computers, checked it with different browsers.
Used firebug to find any error, but HS2 is just not there. It appears only on the first content type.

Can you do me a favor?
Can you add a test content type to your HS demo site and assign eg. your car vocabulary to it?

If it's working on your site (with beta2 / multiselect) it have to be my bad charisma that the module isn't working on my sites...

Sorry, for the late reply.
I have only a local installation at the moment, but i tested HS without CT and it seems to work fine.
I agree that the errors are caused by content_taxonomy and not by HS2.