This code determines which views can be used for pagers:

    $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?

Comments

eigentor’s picture

eigentor commented

Uh, I also bumped into this.

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

robhamm’s picture

robhamm commented

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.

WesleyTx’s picture

WesleyTx commented

subscribing

valderama’s picture

valderama commented

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