Previous/Next for a Views list

Joao

I worked with you before on the adsense module, and like your work, and the way you work.

I granted you CVS access to the prev_next module. Feel free to commit this patch.

I'm not sure if this is the best approach. Storing data like this in the session doesn't seem like a good idea and can often lead to unpredictable results. Also it means that your page can no longer be cached.

Node views are always based on a node so you could provide an option in the configuration screen to index on a view in stead of content types. You could also dynamically generate a prev_next tracking table per view.

prev_next_views implements highly desirable functionality however it is rather fragile and may fail if a page causes nodes in addition to the view data node to be loaded (seeing a non view node the module assumes that we have navigated away from our view data and deletes the session key).

The attached patch caches all node ids as they are loaded and only deletes the session data in hook_exit if a matching node is not found.

In addition the patch implements a more fully featured view node pager which includes configurable first , prev, next and last node links. A current position indicator is also included as is a link back to the original view (this works with view arguments and exposed filters).

function prev_next_pager(&$node, $pager_options) has been added to prev_next.module. This calls hook_prev_next_pager which is implemented in prev_next_views.module.

A view node pager is created like so.

  // get the prev/next module view node pager.
  // define view to be paged in prev next views nodule
  $pager_options = array('first'=> array('text' =>'« first'), 
  					     'prev'=>  array('text' =>'‹ previous'), 
  					     'current'=> array(), 
  					     'next'=>  array('text' =>'next ›'),  
  					     'last'=>  array('text' =>'last »'),
                         'view_url' =>  array('text' => '« back to search')
  ); 					     
  $pager = prev_next_pager($node, $pager_options);
  $vars['prev_next_pager'] = $pager;

I usually insert it in a preprocess function but it could be inserted in hook_nodeapi $op=view in the way that the print module links are - though that would change the module from being purely an api.

The patch also defines two theme functions:

 function theme_prev_next_views_node($node, $link_text); 
function theme_prev_next_views_pager($pager); 

The first enables theming of individual node links.
The second manages theming of the entire pager.

muggin code work really great.
The module by it self doesn't work well with active cache, and with this patch work like a charm.

This should be integrated in the module.

Hi,

I have a view with few exposed filters. When a user performs a search, it will display a set of images as per the search criteria and each image is linked to it's content. If a user clicks on an image, it will direct the user to the corresponding content page but I need to let the user to go back to search results or to navigate to previous/next search items from there.

Can this be done using this module with the suggested patch by mugginsoft.net? It would be great if someone can assist me to achieve this.

I'm fairly new to Drupal and any help would be very much appreciated.

Thank you.
lavms

Views navigation is an answer to that.

Feel free to reopen if needed.