Suppose I have the following vocabulary tree, and I check the terms as indicated:

X term 1
X -term 1.1
_ -term 1.2
_ term 2
X -term 2.1
_ -term 2.2

Since the parent of term 2.1 is not checked, the term itself is not checked. This is unwanted since:
- later reshuffling of a tree might cause term to fall out of scope.
- Views exposed filters does provide the expected behaviour.

Comments

bartk’s picture

Status: Active » Postponed (maintainer needs more info)

I'm not sure I understand you correctly:

Since the parent of term 2.1 is not checked, the term itself is not checked.

What do you mean by "not checked"? When I save a node with an unchecked parent item that has a checked child item, the child item saves correctly.

johnv’s picture

IIRC, i meant saving the terms on the field settings page, to determine the terms that show up on the node edit page. (sorry for not stating it earlier) if you then shuffle the term tree, you get unexpected results on the node edit page.

johnv’s picture

Status: Postponed (maintainer needs more info) » Active
bartk’s picture

Status: Active » Postponed (maintainer needs more info)

I can't replicate this issue. When I set a default on the settings page, then move the term in the taxonomy tree, the correct default terms are still selected.

I think this used to be a bug in an earlier version, and I haven't touched 2.x-dev for a long time. If this is still happening, try switching to the latest stable version.

If it's happening on 1.8, I need more detailed steps on how to replicate the bug, as it's entirely possible that I still don't understand what you're getting it. :)

Bart

bartk’s picture

Status: Postponed (maintainer needs more info) » Fixed

Still can't replicate. I'm assuming at the moment that this is fixed, since you reported this on an old dev tree. If you can give me steps to replicate it on 1.9, please reopen this report.

Thanks,
Bart

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.