Download & Extend
Custom Pagers » Issues

Is the limitation to views with fields artificial with Views 2?

Posted by robertDouglass on February 4, 2009 at 3:43pm
Project:Custom Pagers
Version:6.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

This code determines which views can be used for pagers:

<?php
    $all_views = views_get_all_views();
    foreach ($all_views as $view) {
      // Only views that have fields will work for our purpose.
      if (!empty($view->display['default']->display_options['fields']) && $view->base_table == 'node') {
        $options[$view->name] = $view->name;
      }
    }
?>

Is this an artificial limitation for Views 2? Do views really need fields to be viable for pagers?

Login or register to post comments

Comments

#1

Posted by eigentor on March 10, 2009 at 8:53pm

Uh, I also bumped into this.

So I cannot user custom pagers on views that just show teasers or full nodes?

#2

Posted by robhamm on April 24, 2009 at 9:44pm

There is a quick and easy workaround for this. Create your view as a fields view, set up your custom pagers, THEN switch your view back to node. Voila! The custom pagers still show up.

#3

Posted by WesleyTx on May 28, 2009 at 3:33am

subscribing

#4

Posted by valderama on January 20, 2011 at 5:15pm

i am using this module with "non-field" views without any problems. so i wonder if this this check against field-views could be removed in the next version?

best,
walter