CT vocabulary terms not displaying properly

Same 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

Same problem here. Any ideas?

It 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.

function _panels_content_vocabulary_terms($tid, $max_depth, $depth = -1) {
  $depth++;
  if ($max_depth != NULL && $depth == $max_depth) {
    return array();
  }
  $return = array();
  $query = db_query('SELECT t.name, t.tid FROM {term_data} t INNER JOIN {term_hierarchy} h ON t.tid = h.tid WHERE h.parent = %d', $tid);
  while ($result = db_fetch_object($query)) {
    $return[] = array(
      'data' => l($result->name, 'taxonomy/term/'. $result->tid),
      'children' => _panels_content_vocabulary_terms($result->tid, $max_depth + 1, $depth),
    );
  }
  return $return;
}

Hi,

Did somebody already solve this one? Please post your solution code!
Thanks a lot in advance!
greetings, Martijn

Still happens with beta4b.

Confirmed. There's indeed about everything wrong with this code, it definitely needs to be rewritten.
I'll take a look at it next week.

Here'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.

This patch fixed it for me! Awesome Pancho!

Applied. Thanks!