You are here

Home » API reference » Recently Read 7.3

README.txt in Recently Read 7.3

Same filename and directory in other branches
  1. 8 README.txt
  2. 6 README.txt
  3. 7 README.txt
  4. 7.2 README.txt
// $Id$

== SUMMARY ==

The Recently Read module displays the history of recently read Entity
a particular user has viewed. Each authenticated user has its own history 
recorded, so this module may be useful i.e. for displaying recently viewed 
products on the e-commerce site. The history is displayed as a block and each 
content type gets its own block.

If you need more flexibility, this module can be replaced by properly configured
Flag, Rules and Views modules. Check out the following links for more details:
* http://drupal.org/node/405754
* http://jan.tomka.name/blog/list-recently-viewed-nodes-drupal

For a full description of the module, visit the project page:
  http://drupal.org/sandbox/pgorecki/1080970

To submit bug reports and feature suggestions, or to track changes:
  http://drupal.org/project/issues/1080970


== REQUIREMENTS ==

None.


== INSTALLATION ==

* Install as usual, see http://drupal.org/node/70151 for further information.
* Module depend on module views, entity, session_api. Pls download it accordingly.
  http://drupal.org/project/views
  http://drupal.org/project/entity
  http://drupal.org/project/session_api


== CONFIGURATION ==

  Just an example for recently viewed nodes. Actually, all the recently read entity can support.
  1: Add a new views based on node(content).
  2: set a relationship "Recently Read".
  3: Add filter:
     (Recently Read) Recently Read: Current (Yes)
     (Recently Read) Recently Read: entity type (= Node)
  4: Add sort:
     (Recently Read) Recently Read: Recently Read Date (desc)
  5: Maybe you can create a views block. and in block configuration page, you can place this block
  where you want. 
     Or you can use context module, to make a better block visibility config.

  If you use this module in your commerce site, you can create recently read orders based on this tutorial.


== CONTACT ==

Current maintainer:
* Przemyslaw Gorecki (pgorecki) - http://drupal.org/user/642012
* Terry Zhang (zterry95) - http://drupal.org/user/1952394

File

README.txt
View source 
  1. // $Id$

  2. 

  3. == SUMMARY ==

  4. 

  5. The Recently Read module displays the history of recently read Entity

  6. a particular user has viewed. Each authenticated user has its own history 

  7. recorded, so this module may be useful i.e. for displaying recently viewed 

  8. products on the e-commerce site. The history is displayed as a block and each 

  9. content type gets its own block.

  10. 

  11. If you need more flexibility, this module can be replaced by properly configured

  12. Flag, Rules and Views modules. Check out the following links for more details:

  13. * http://drupal.org/node/405754

  14. * http://jan.tomka.name/blog/list-recently-viewed-nodes-drupal

  15. 

  16. For a full description of the module, visit the project page:

  17.   http://drupal.org/sandbox/pgorecki/1080970

  18. 

  19. To submit bug reports and feature suggestions, or to track changes:

  20.   http://drupal.org/project/issues/1080970

  21. 

  22. 

  23. == REQUIREMENTS ==

  24. 

  25. None.

  26. 

  27. 

  28. == INSTALLATION ==

  29. 

  30. * Install as usual, see http://drupal.org/node/70151 for further information.

  31. * Module depend on module views, entity, session_api. Pls download it accordingly.

  32.   http://drupal.org/project/views

  33.   http://drupal.org/project/entity

  34.   http://drupal.org/project/session_api

  35. 

  36. 

  37. == CONFIGURATION ==

  38. 

  39.   Just an example for recently viewed nodes. Actually, all the recently read entity can support.

  40.   1: Add a new views based on node(content).

  41.   2: set a relationship "Recently Read".

  42.   3: Add filter:

  43.      (Recently Read) Recently Read: Current (Yes)

  44.      (Recently Read) Recently Read: entity type (= Node)

  45.   4: Add sort:

  46.      (Recently Read) Recently Read: Recently Read Date (desc)

  47.   5: Maybe you can create a views block. and in block configuration page, you can place this block

  48.   where you want. 

  49.      Or you can use context module, to make a better block visibility config.

  50. 

  51.   If you use this module in your commerce site, you can create recently read orders based on this tutorial.

  52. 

  53. 

  54. == CONTACT ==

  55. 

  56. Current maintainer:

  57. * Przemyslaw Gorecki (pgorecki) - http://drupal.org/user/642012

  58. * Terry Zhang (zterry95) - http://drupal.org/user/1952394