possibly this is more a bug with the usernode module; but some of the behaviour sounded a bit odd for the category module as well so thought i would post here as well.

With the category module (rather than the taxonomy module) i can allow other node types to be categories (terms).

Example using "page" nodes as categories in a container (vocabulary) call "Pages" to tag "image" nodes. I create a container called Pages and allow the type "page" to be turned into a term in that vocab. When i do this all works as it should:

- create page with title "test1"
- appropriate terms get created in both the category tables and the term (taxonomy) tables
- when i go to create an image i am allowed to tag it with items from the Page container which now magically includes my new term called "test1"

The same scenario with usernodes:

- container called "Users"
- usernodes allowed to be categories in the Users container

- create a new user (tom)
- usernode gets created
- a category gets created in category table called tom BUT its parent is 0 and it should the nid of the container Users
- nothing gets created in the matching taxonomy tables
- first time i edit the usernode and simply hit submit with no changes the category table gets corrected and it is now under the right container
- but the term table is still wrong - i think this is because on first edit the usernode's container is set to Users which is why the cat table gets fixed; but the parent is set to Root which is why the term table record doesn't get created.
- on the 2nd edit the root now appears as Users and when the usernode is submitted again; the term table record now gets created.

This does seem a little like a category module issue except for the fact that everything works correctly when other node types are created - so my guess would be when the usernode gets created it either jumps out of the normal hook flow at some point or isnt using the hook system to add the node in the first place.

Peter Lindstrom
LiquidCMS - Content Management Solution Experts