Posted by ElleKitty on April 29, 2009 at 5:35am
| Project: | Custom Pagers |
| Version: | 6.x-1.10-beta1 |
| Component: | Documentation |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I'm in the process of converting my portfolio site to Drupal. So far I have several grid views of images (with requisite CCK type) and each of them has a pager. I'm adding a blog-like "Sketchbook" to post WIPs in. I've made the view for the sketchbook as a simple node list and have it displayed as a page. However unlike the gallery views, the sketchbook view doesn't show in the list of views avalible to make custom pagers with.
Can offer more info given the right questions. Site in progress is http://www.themindstream.net/sandbox/drupal
Comments
#1
I can confirm this.
Two of my views are not shown in select box.
I cannot detect a pattern, why most views are shown and some others not.
These views are "normal" node-views and using no arguments.
Has anyone an idea?
Thanks in advance,
Ralf
#2
In custom_pagers_form() (in file custom_pagers.admin.inc), the module checks to see of the view has output fields set. Does your view use the "Fields" or the "Nodes" row style?
if (!empty($view->display['default']->display_options['fields']) && $view->base_table == 'node') {$options[$view->name] = $view->name;
}
What worked for me as a workaround was to switch the view to "Fields" rowstyle first, add some fields to the view, and save it. Then you can select it in custom pagers admin. Once the view has some fields added, it looks like you can change the rowstyle back to "Nodes".
#3
Thanks, the workaround did the trick.
#4
This workaround work-arounded for me.
Just switch the view type to fields, add add a field (don't even save) then switch it back to node and save. Bam, it's in the list.
#5
Thanks, worked for me too!
#6
Sounds like this is a documentation bug. Here's a patch that changes the text below the field to call out the fact that your view must have fields. hopefully it will save the next guy the 10 minutes I spent googling this :)
#7
That's one way, I suppose, but it would be extra-nice if the module could be written so it worked both ways. I don't actually know whether or not that's feasible.