Howto: Flip columns and rows in table output

You could do this with a table view and by theming the view "flip" the default presentation of the information.

There is no way to do this in the UI, but as nevets says, you can theme the view and restructure the output as you like. This is a fairly complex task as it uses tables and in Views 1 tables are kind of a pain to theme, but it is possible.

Ok, make a table view, make sure it works. Then add the following function in your themes template.php file. You will need to replace VIEWNAME with your views name.

function phptemplate_views_view_table_VIEWNAME($view, $nodes, $type) {
  $fields = _views_get_fields();

  $r = 0;
  
  foreach ( $view->table_header as $header ) {
  	$rows[$r][] = $header;
  	$r++;
  }
  
  $r = 0;
  foreach ($view->field as $field) {
    if ($fields[$field['id']]['visible'] !== FALSE) {
    	foreach ($nodes as $node) {
	      $cell['data'] = views_theme_field('views_handle_field', $field['queryname'], $fields, $field, $node, $view);
	      $cell['class'] = "view-field ". views_css_safe('view-field-'. $field['queryname']);
	      $rows[$r][] = $cell;
	    }
	    $r++;
    }
  }
  return theme('table', array(), $rows);
}

Just popping in to say "thank you" to nevets for helping out! It's appreciated!

Can someone add this to the handbooks, please?

Hmm, tried this code, didnt work. using drupal 6 and views 2

Version: 5.x-1.6

That's why.

So then the code must be different! Tell me!

please and thankyou.

Subscribing, interested in this too.

I'm interesting too. There is also this http://drupal.org/node/174578#comment-819915 but it's for Drupal 5.X.

Someone know so how to flip columns and rows with drupal 6.x and with Wiews2 ?

Thanks :)

I'm trying to do this with a view created with the editablefields module http://drupal.org/project/editablefields using the view type "Editablefields - table- no form". I got the function posted in this thread to work properly on a regular table view. I also got it to apply to the editablefield table view by changing the function name to:

function phptemplate_views_editablefields_view_table_noform_VIEWNAME($view, $nodes, $type) {

I can see that it's worked properly on the first two rows but all of the editable fields do not display. I assume that it's because it's a different function that's being overwritten than what the flip-column/row code was originally written for.

I think this is the function from the editablefields module:

/**
 * Display the nodes of a view as a table.
 */
function theme_views_editablefields_view_table_noform($view, $nodes, $type) {
  $fields = _views_get_fields();

  $editable=_handle_editablefield_form_input($view, $nodes);

  foreach ($nodes as $node) {
    $row = array();
    foreach ($view->field as $field) {
      if ($fields[$field['id']]['visible'] !== FALSE) {
        $cell['data'] = views_theme_field('views_editablefields_handle_field', $field['queryname'], $fields, $field, $node, $view);
        $cell['class'] = "view-field ". views_css_safe('view-field-'. $field['queryname']);
        $row[] = $cell;
      }
    }
    $rows[] = $row;
  }
  $html=theme('table', $view->table_header, $rows );
  
  if ($editable) {
      if ($nodes) {
	$form['editablefields-d-'.$view->name]['submit']= array('#type' => 'submit', '#value' => t('Update'));
	$form['editablefields-d-'.$view->name]['#value']=$html;
	drupal_process_form('editablefields-d-'.$view->name,$form);
	$eform=drupal_render($form);
	return $eform;
      }
    }
    return $html;
}

Is there anyone who could re-write this flip-column/row code to apply to views of this type?

Subscribing. Also very interested in a Views2/ Drupal 6 solution. Doesn't appear that http://drupal.org/node/174578 applies to Views 2.

In my case the main use would be for charts. None of existing Drupal chart modules provide functionality for flipping columns/ rows.

I have not tried the module but people following this thread might find Views Crosstab useful

Original issue resolved with themeing/editable fields. If this is also a 2.x issue, a separate issue should be logged and referred back to this one as appropriate.