Selection only saved if it has children

Hi, and thanks for listening!
I added a level to the top, which didn't help, sadly. It still seems that only the bottom level terms are stored. Again, i guess i can work around it by adding children to every "single parent".

The only way I know to dump a vocab is with the xml import/export module, so i attached an export. Educate me if you meant something else.

Here is the vocab as shown in vocab editing, all terms, after adding the top level. Of these, i can save f.ex "Artist Group" or "Main Partners" or "Electronica", but "Administration" or "Board Members" does not save.

Hovedkategorier
-- Administration
-- Artists
---- Artist Group
---- Author
---- Dance&Stage production
---- Film
---- Musician or Band
---- Organization
---- Visual Artist
-- Board Members
-- Companies&Organizations
-- Partners
---- Main partners
---- Other partners
-- Programme&Curators
---- Live Art
---- Music
------ Elektronika
------ Indie Nights
------ Innbrudd
------ Murstein
---- Tou Kunsthall
---- Tou Vindu
---- Tou Works
-- Stockholders
---- Artist Stockholders
-- Service Providers

Indeed, no problems after adding children to all the top level terms. (Eg. Administration, Board Members, etc..)

Now, if only I didn't have to maintain two, soon three separate but identical vocabs so that items can be listed in separate categories. Are there no modules using Hierarchical Select, but store data in cck fields?

And one more question on this open line: other issue-posts under HS have referred to moving or updating a javascript, one post I think mentioned jquery.js. I haven't seen any reference to this in the readme, nor anything more specific in the issues. Is this just an antiquated requirement? I have interface.js, of course.

Not quite true, "no problems"... After a while of feeding and recategorizing my items, I discovered that there are some selections that just won't save.
No matter what I select under "Artists", the node is saved with "Artist Group"; no matter what I select under ANY parent, the node is saved with the first child. So I am able to traverse down to:

-- Programme&Curators
---- Live Art
---- Music
------ Elektronika
------ Indie Nights

... and select "Indie Nights", but "Elektronika" is saved.

Also, if i first save "Elektronika", i am subsequently unable to save the node with "Live Art". The term remains unchanged until i save with a term from a different branch in the hierarchy, f.ex "Partners"->"Main Partners".

Aiiiii.

Is there a way to intercept the data posted from the node form? Or do I need to monitor the DOM? I have no concrete reasons but suspect this is rooted in some js. I'll see what happens if i disable all other js-providing modules.

Holy flying ****. I'm sorry. I had neglected jquery_update, upstream of jquery_interface: it caused problems for an other script, so i had reverted the jquery.js to core drupal 5.2 without disabling the module. Old jquery.js was culprit, i was cause.

Everything works just excellent now. Bad kevin, good module.