Closed (fixed)
Project:
Panels
Version:
5.x-2.x-dev
Component:
Plugins - content types
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 Feb 2008 at 21:55 UTC
Updated:
31 Jul 2008 at 04:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawansv commentedSame issue here. I have 4 different vocabularies, and when selecting any vocabulary, the title changes, but the term list is always the same: all terms from all vocabularies.
Also:
- terms seem to be sorted in database order instead of using the weight factor.
- only first-level terms show up, whether I leave max depth to blank (supposed to mean unlimited) or specify a depth of 2 or 3 (I have 2 levels in my case).
Cheers,
Vincent
Comment #2
nath commentedSame problem here. Any ideas?
Comment #3
nath commentedIt seems to me that the problem is in this function in vocabulary_terms.inc. There is no limitation to a single vocabulary in that function.
If one wants to show all terms in a vocabulary, $tid will be 0 and so the result of thee query is a list of all top-level terms in all vocabularies.
Comment #4
summit commentedHi,
Did somebody already solve this one? Please post your solution code!
Thanks a lot in advance!
greetings, Martijn
Comment #5
nath commentedStill happens with beta4b.
Comment #6
panchoConfirmed. There's indeed about everything wrong with this code, it definitely needs to be rewritten.
I'll take a look at it next week.
Comment #7
panchoHere's a list with all bugs:
1. 'max_depth' field is generally not saved.
2. If 'tree' is set to true:
- output is not restricted to a certain vid
- 'max_depth' == 0/empty shows only top level (instead of all levels)
- 'max_depth' > 0 shows all levels (no restriction)
- terms are not ordered, term weight is ignored
(If 'tree' is set to false, everything is fine.)
Enclosed patch fixes all of this, and renders 'max_depth' as a select instead of a textfield to improve usability.
Comment #8
panchoComment #9
Fayna commentedThis patch fixed it for me! Awesome Pancho!
Comment #10
merlinofchaos commentedApplied. Thanks!
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.