With Drupal 6.10 I am getting the issue that appears to be discussed here:
http://drupal.org/node/275352

From how I read it (especially comment #42) I believe this is the proper course of action. I apologise if not.

When disabling this module, it stops behaving wrong, and the errors go away.

Comments

chiddicks’s picture

chiddicks commented
Status: Active » Closed (won't fix)

There definitely is an issue here since we're mucking about with the core taxonomies form elements and objects in the node array after. But, AFAIK there's no way around that.