You are here

Home » API reference » Views navigation 7

README.txt in Views navigation 7 

CONTENTS OF THIS FILE
---------------------

 * Introduction
 * Limitations
 * Installation
 * Configuration
 * Working

INTRODUCTION
------------

Current Maintainer: Gaël Gosset <ggosset@insite.coop>

This module adds next and previous links on content pages when accessed from a 
view. It is intended for dynamic and/or paged view results, where the result set 
changes according to exposed filters, current user access rights,...

You may need this module if the content which comes after a given content 
depends on context, and more precisely depends on which content list you came 
from.

You may also look at this comparison of next/previous modules:
http://drupal.org/node/1276920

Developed by Insite
www.insite.coop

LIMITATIONS
-----------

Currently only works with the default query plugin or the Search API query
plugin, for views with the following row styles:
* "fields" (supported content fields : Title, Link, Path and Image)
* "rendered entity", with a label linking to the entity page.
All kinds of entities which have their own page are supposed to work,
BUT only the node entity type has been really tested, you may experience some
problems if your view lists users, terms... Please provide feedback if you found
a bug.
Feel free to submit new views handlers based on the code from the existing ones
(it's usually only one class method to override).
* if the view has random sorting, you'll get a random behavior ;)

INSTALLATION
------------

Follow the usual contrib module installation process:
http://drupal.org/documentation/install/modules-themes/modules-7


CONFIGURATION
-------------

On your view's configuration page, in Advanced, there is a new setting to enable
views navigation.
The links are added to the default node template, but there is also a block
available if you need (which is needed for other entity types like terms,
users,...).

WORKING
-------

1. When the view is rendered, its query is stored with a unique ID and the
fields linking to the entities are rendered with an altered URL, where GET
parameters are added to pass the stored query ID and the position of the entity
in the result set.
PERFORMANCE FIRST MODE CHOSEN:
2. When the entity page is rendered, if these GET parameters are set, next and
previous links are added accordingly.
3. When the link is clicked, the stored query is executed (with no paging) to
know which entity is the next/previous.
SEO FIRST MODE CHOSEN:
2. When the entity page is rendered, if these GET parameters are set, the stored
query is executed (with no paging) to know which entity is the next/previous.
Next and previous links are added accordingly.

Of course, these operations are cached for better performances.

File

README.txt
View source 
  1. 

  2. CONTENTS OF THIS FILE

  3. ---------------------

  4. 

  5.  * Introduction

  6.  * Limitations

  7.  * Installation

  8.  * Configuration

  9.  * Working

  10. 

  11. INTRODUCTION

  12. ------------

  13. 

  14. Current Maintainer: Gaël Gosset 

  15. 

  16. This module adds next and previous links on content pages when accessed from a 

  17. view. It is intended for dynamic and/or paged view results, where the result set 

  18. changes according to exposed filters, current user access rights,...

  19. 

  20. You may need this module if the content which comes after a given content 

  21. depends on context, and more precisely depends on which content list you came 

  22. from.

  23. 

  24. You may also look at this comparison of next/previous modules:

  25. http://drupal.org/node/1276920

  26. 

  27. Developed by Insite

  28. www.insite.coop

  29. 

  30. LIMITATIONS

  31. -----------

  32. 

  33. Currently only works with the default query plugin or the Search API query

  34. plugin, for views with the following row styles:

  35. * "fields" (supported content fields : Title, Link, Path and Image)

  36. * "rendered entity", with a label linking to the entity page.

  37. All kinds of entities which have their own page are supposed to work,

  38. BUT only the node entity type has been really tested, you may experience some

  39. problems if your view lists users, terms... Please provide feedback if you found

  40. a bug.

  41. Feel free to submit new views handlers based on the code from the existing ones

  42. (it's usually only one class method to override).

  43. * if the view has random sorting, you'll get a random behavior ;)

  44. 

  45. INSTALLATION

  46. ------------

  47. 

  48. Follow the usual contrib module installation process:

  49. http://drupal.org/documentation/install/modules-themes/modules-7

  50. 

  51. 

  52. CONFIGURATION

  53. -------------

  54. 

  55. On your view's configuration page, in Advanced, there is a new setting to enable

  56. views navigation.

  57. The links are added to the default node template, but there is also a block

  58. available if you need (which is needed for other entity types like terms,

  59. users,...).

  60. 

  61. WORKING

  62. -------

  63. 

  64. 1. When the view is rendered, its query is stored with a unique ID and the

  65. fields linking to the entities are rendered with an altered URL, where GET

  66. parameters are added to pass the stored query ID and the position of the entity

  67. in the result set.

  68. PERFORMANCE FIRST MODE CHOSEN:

  69. 2. When the entity page is rendered, if these GET parameters are set, next and

  70. previous links are added accordingly.

  71. 3. When the link is clicked, the stored query is executed (with no paging) to

  72. know which entity is the next/previous.

  73. SEO FIRST MODE CHOSEN:

  74. 2. When the entity page is rendered, if these GET parameters are set, the stored

  75. query is executed (with no paging) to know which entity is the next/previous.

  76. Next and previous links are added accordingly.

  77. 

  78. Of course, these operations are cached for better performances.