Alphabetic summary listing of node titles causes SQL error

Hmm. Odd that the code is like that. Your changes definitely appear correct.

Getting the same or a similar error and it looks like something broken in the views_handler_arg_nodeletter argument code. I create a simple view with the node title as the only field and node title as the only argument, no other fields, or sorts or filters, and get the following error. Notice that 'node.' is getting prefixed to the node title field making it 'node.node.title' -- the same part of the query that is getting mangled in the example above.

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.title FROM node node WHERE (node.type IN ('content_events')) GROUP BY node.tit' at line 1 query: pager_query SELECT node.title AS letter, count( DISTINCT(node.nid)) AS num_nodes, node.node.title AS letter_node.title FROM node node WHERE (node.type IN ('content_events')) GROUP BY node.title, letter_node.title ORDER BY letter_node.title ASC LIMIT 0, 10 in C:\wamp\www\home\includes\database.mysql.inc on line 172.

The posted fix doesn't help my situation, still playing around trying to figure out exactly what is broken here...

A little more info -- my simple example above creates broken sql only if 'summary unsorted', 'summary sorted ascending' or 'summary sorted descending' is selected, 'summary sorted as view' works fine as do all views that do not add summaries. The only difference between the summaries that don't work and the one that does is that $self-sort is set on the broken summaries and not on the one that works right. I'm stuck at this point trying to figure out why the setting of $self-sort is adding an unwanted prefix to the field when this particular argument is used.

Should change the status...

Anyway, it turns out the difference between the summaries that use $self-sort and the one that does not is that the queries that use $self-sort add an alias of 'letter' to the query while the 'summary sorted as view' gets created a different way which does not set the alias. The summaries then run through add_orderby() where an alias is prefixed to our summaries and a field with that alias is added to the view.

The summary that works adds no alias when run through this function, which for some reason creates an alias of 'node_changed', which works correctly, while the 'letter' alias does not, so somewhere in here is where the query is getting garbled.

Something in this code is just not handling aliases right, but I'm not sure I know what all might be affected by changing this code, so I hesitate to suggest a fix. My workaround for now is to use 'summary sorted as view' instead of the broken summaries since that summary does not add a broken field to the query. I can get it to sort right by adding Node:Title to the sort, so that 'summary sorted as view' has the sorting I originally wanted.

/*
   * Add multiple an orderby's. Right now I'm not sure why this function
   * is separate from add_orderby above; I don't think it needs to
   * be.
   *
   * NOTE: $alias doesn't work when adding multiple orderbys.
   */
  function add_orderby($table, $field, $order, $alias = '') {
    if (!$alias && $table) {
      $alias = $this->use_alias_prefix . $table;
    }
    elseif ($alias) {
      $alias = $this->use_alias_prefix . $alias;
    }

    if ($table) {
      $this->ensure_table($table);
    }

    if (!is_array($field)) {
      $field = array($field);
    }

    foreach($field as $f) {
      // Only fill out this aliasing if there is a table;
      // otherwise we assume it is a formula.
      if ($table) {
        $as = $alias . '_' . $f;
      }
      else {
        $as = $alias;
      }
      $this->add_field($f, $table, $as);
      $this->orderby[] = "$as $order";
      if ($this->groupby) {
        $this->add_groupby($as);
      }
    }
  }

Nobody's touched this issue in a year and a half, and nobody's working on 1.x, I'm won't fixing this.