When I publish a new node and assign it hierarchical terms, the correct lineage is saved (see Snap2.gif), the lineage is
Hierarchy: 0007-Business & Commercial 0000-Alaska Business & Commercial0001-Internet Providers' Information

If I edit this node, part of the lineage is lost (see Snap3.gif), and the lineage changes to
Hierarchy: 0007-Business & Commercial 0000-Alaska Business & Commercial

a) How can I prevent this from happening?
b) Would if have something to do with the fact that there isn't a space between the second and third terms? e.g., Alaska Business & Commercial0001

Comments

stinky’s picture

StatusFileSize
new2.75 KB
new3.22 KB

I forgot to attach the screen shots....

stinky’s picture

StatusFileSize
new1.18 KB
new1.54 KB

Found some more info.
If I'm logged in as user 1 (the admin), the view displays correctly (snap4.gif)
Hierarchy: 0007-Business & Commercial 0000-Alaska Business & Commercial 0001-Internet Providers' Information

If I'm logged in as any other user, or not logged in at all, the view displays with the abbreviated hierarchy (snap5.gif).
Hierarchy: 0007-Business & Commercial 0000-Alaska Business & Commercial

stinky’s picture

Ugh. This is what I was experiencing in http://drupal.org/node/864630
However this time the display is correct when the node is first published. It displays incorrectly after a node edit.

xjm’s picture

What version of TAC are you using? Could be related to a TAC bug.

el1_1el’s picture

StatusFileSize
new9.83 KB
new4.36 KB
new6.75 KB
new14.49 KB

I think I may be having a similar issue, although it is happening with all users including user1.

I am sequencing in views based on a taxonomy structured like taxonomy.gif. On some of my nodes, the entire hierarchy is coming through into the view (hierarchy.gif), while in most the last term in the hierarchy is absent (hierarchy1.gif). I am also using TAC 6.x-1.3, and I have tried disabling and uninstalling Lineage and then re-enabling several times. I don't think the view is the issue but I attached just in case it would help. One other possible issue is that I imported some of the taxonomy terms using the Node Import module....but they seem fine in tax core and manager and its happening on terms that were added manually as well.