I just created a View Tree that, while logged in as UID 1, shows up in the expected order (a sort for Taxonomy Weight was added), but when viewed by an anonymous user, shows up as if the hierarchy created in Taxonomy is flat.

Example:

Hierarchy in Taxonomy:
Term 1 (weight: 0)
Term 2 (weight: 1)
- Term 3 (weight: 0)
- Term 4 (weight: 1)
- Term 5 (weight: 2)
Term 6 (weight: 2)
Term 7 (weight: 3)
Term 8 (weight: 4)
- Term 9 (weight: 0)
Term 10 (weight: 5)
- Term 11 (weight: 0)
- Term 12 (weight: 1)

shows up for anonymous users as:
Term 11
Term 9
Term 3
Term 1
Term 4
Term 2
Term 6
Term 5
Term 7
Term 8
Term 10

Comments

greatmatter’s picture

greatmatter CreditAttribution: greatmatter commented

Ah, it also does not show parent element elements consistently.

greatmatter’s picture

greatmatter CreditAttribution: greatmatter commented

While attempting to figure this out, I've found that Views adds a bunch of stuff from the Node Access (na) table to the end of the non-UID:1 query. So, I disabled Query Rewriting, and it seems to be an appropriate workaround for my purposes... Still, something's up.

marcissimus’s picture

marcissimus CreditAttribution: marcissimus commented
Issue summary: View changes

This works just as designed. You have to explicitly add a "Sort criteria" for "Taxonomy term: Weight (asc)". Please test so we can close this issue