"Show node counts" does not work (all counts show as zero) unless "Show nodes" is also enabled. Same results whether Views are used or not. In case it makes a difference, this is a treemenu built on a two level hierarchical taxonomy with some terms having multiple parents, for example:
Subdivision 1
--Council District 1 (*)
--Fire District 2
--Legislative District 3
Subdivision 2
--Council District 1 (*)
--Fire District 4
--Legislative District 9
Comments
Comment #1
rcrowther commentedRight. Cheers for the detail, because sometimes it makes all the difference. In this case, no, because after some agonizing I put a rock solid, separately searched node count in, as that feature is so important to people nowadays.
I figure something must be going wrong with the database query itself. And I can't replicate your error - this works fine on my setup - which is going to make this tricky.
It depends on how far you'd like to go. For starters, try turning off any node access or permission stuff, see if that switches things back on. Anything to do with hunting nodes out of the database. If you can find me a module or setup that triggers this, I'll gladly work on it.
If you know a even a little code, post, and I'll get more suggestions to you.
Comment #2
Golem07 commentedI had the very same problem.
Updating to the latest 6.2 release (which worked smoothly) solved this immediately. Everything seem to work as it is intendet to.
Thanx for a great module!
Comment #3
rcrowther commentedHo, when this module is suffering it's oh-so-public traumas, where you there (I guess so!)?
Seriously, though, this is interesting. I wonder if the query caching (sadly disabled, but not THAT valuable a saving) was the problem. If your upgrade went ok, that's a real positive, and a new one, and thankyou for posting. Can anyone confirm Golem's experience, and let me close this one?
Comment #4
BayouBill commented"Can anyone confirm Golem's experience..."
Confirmed. Core 6.13, TTM 6.2.
Comment #5
rcrowther commentedAce. Marking as fixed. Rob.