Views is great at steps 1-3 below, but I'd love to see support added for 4 & 5.

A user performing a search on a generic website follows a typical path:

1. make selection from search terms
2. scroll through list of results
3. click on a matching entry and view detail for one result (in Drupal, a node)
4. continue navigating through list from 'detail' screen with next / prev links
5. return to list
6. go back to 1

But as far as I can tell, 4 & 5 aren't possible with views. eg our Drupal site has several thousand photos, and each one is a node. You can get to a photo node from a variety of different views (search by tag, by date, etc), but once you hit the photo node you've lost any connection to the view that sent you there. To see another photo in the list of results you have to hit the browser's back button to get back to the view.

The Custom Pagers module looks like it was written with this problem in mind, but as far as I can see it can't handle views with exposed filters such as this: http://gwulo.com/catalog

Are there any plans to support this? Or even better, is it there already and I don't know how to do it?

Thanks & regards, David

Comments

dawehner’s picture

Project: Views (for Drupal 7) » Previous/Next API
Version: 6.x-2.9 » 6.x-1.x-dev
Status: Active » Closed (duplicate)

This is way to specific for a generic module as views.

The prev/next problem is not that easy to solve. There is as module which has a api: http://drupal.org/project/prev_next

There is a feature request there already, see http://drupal.org/node/662362