You are here

README.txt in Panels Content Cache 7

Panels Content Cache
--------------------
This module provides a cache plugin for Panels, Panelizer and other
CTools-based display systems. The primary goal of the module is to cache panes
and pages indefinitely until content belonging to one of the selected content
types is either created, modified or deleted, at which point that pane is
reloaded.

This version of the module only works with Panels 7.x-3.4 and newer.


Features
------------------------------------------------------------------------------
The primary features include:

* Support for all Page Manager (CTools), Panels and Panelizer displays.

* Clear the cache for the configured pane when content belonging to selected
  content types is created, modified or deleted.

* Supports the core Comment module, so comments posted to one of the configured
  content types will also clear the caches.

* Additional options to fine tune the cache granularity:

  * Current URL.
    * Provides several options to accommodate different scenarios.

  * Page arguments.

  * Panels contexts.

  * Active user.
    * This will create a separate cache object for each user and is usually
      unnecessary.

  * Active user's roles.
    * This allows for creating a separate cache instance based upon the current
      user's roles. This is particularly useful when using the Contextual
      module, to avoid the context menus showing for the wrong users.
    * It is possible to select which roles will be given the same cached object
      as the anonymous user; it is suggested to select the "Authenticated user"
      role on scenarios when a "normal" logged in user would not gain any extra
      access to the content.
    * In the interest of performance, it is possible to trigger caching based
      on a complete list of all a given user's roles, just the first one or
      just the last one; the default is to consider all of a user's roles.

  * The current domain, as configured through Domain Access.


Related modules
------------------------------------------------------------------------------
Some available modules are similar or related to Panels Content Cache:

* Cache Consistency
  https://www.drupal.org/project/cache_consistent
  Sites using something other than the database for cache storage, e.g.
  memcached, may run into a bug in Drupal core that triggers a race condition
  in the cache_field bin. This module provides a work-around and is in use
  on drupal.org. See https://www.drupal.org/node/1679344 for further details.

* Panels Hash Cache
  https://www.drupal.org/project/panels_hash_cache


Credits / Contact
------------------------------------------------------------------------------
Currently maintained by Damien McKenna [1]. Originally written by Graham Taylor [2].

Ongoing development is sponsored by Mediacurrent [3].

The best way to contact the maintainers is to submit an issue, be it a support
request, a feature request or a bug report, in the project issue queue:
  http://drupal.org/project/issues/panels_content_cache


References
------------------------------------------------------------------------------
1: https://www.drupal.org/u/DamienMcKenna
2: https://www.drupal.org/u/tayzlor
3: http://www.mediacurrent.com/

File

README.txt
View source
  1. Panels Content Cache
  2. --------------------
  3. This module provides a cache plugin for Panels, Panelizer and other
  4. CTools-based display systems. The primary goal of the module is to cache panes
  5. and pages indefinitely until content belonging to one of the selected content
  6. types is either created, modified or deleted, at which point that pane is
  7. reloaded.
  8. This version of the module only works with Panels 7.x-3.4 and newer.
  9. Features
  10. ------------------------------------------------------------------------------
  11. The primary features include:
  12. * Support for all Page Manager (CTools), Panels and Panelizer displays.
  13. * Clear the cache for the configured pane when content belonging to selected
  14. content types is created, modified or deleted.
  15. * Supports the core Comment module, so comments posted to one of the configured
  16. content types will also clear the caches.
  17. * Additional options to fine tune the cache granularity:
  18. * Current URL.
  19. * Provides several options to accommodate different scenarios.
  20. * Page arguments.
  21. * Panels contexts.
  22. * Active user.
  23. * This will create a separate cache object for each user and is usually
  24. unnecessary.
  25. * Active user's roles.
  26. * This allows for creating a separate cache instance based upon the current
  27. user's roles. This is particularly useful when using the Contextual
  28. module, to avoid the context menus showing for the wrong users.
  29. * It is possible to select which roles will be given the same cached object
  30. as the anonymous user; it is suggested to select the "Authenticated user"
  31. role on scenarios when a "normal" logged in user would not gain any extra
  32. access to the content.
  33. * In the interest of performance, it is possible to trigger caching based
  34. on a complete list of all a given user's roles, just the first one or
  35. just the last one; the default is to consider all of a user's roles.
  36. * The current domain, as configured through Domain Access.
  37. Related modules
  38. ------------------------------------------------------------------------------
  39. Some available modules are similar or related to Panels Content Cache:
  40. * Cache Consistency
  41. https://www.drupal.org/project/cache_consistent
  42. Sites using something other than the database for cache storage, e.g.
  43. memcached, may run into a bug in Drupal core that triggers a race condition
  44. in the cache_field bin. This module provides a work-around and is in use
  45. on drupal.org. See https://www.drupal.org/node/1679344 for further details.
  46. * Panels Hash Cache
  47. https://www.drupal.org/project/panels_hash_cache
  48. Credits / Contact
  49. ------------------------------------------------------------------------------
  50. Currently maintained by Damien McKenna [1]. Originally written by Graham Taylor [2].
  51. Ongoing development is sponsored by Mediacurrent [3].
  52. The best way to contact the maintainers is to submit an issue, be it a support
  53. request, a feature request or a bug report, in the project issue queue:
  54. http://drupal.org/project/issues/panels_content_cache
  55. References
  56. ------------------------------------------------------------------------------
  57. 1: https://www.drupal.org/u/DamienMcKenna
  58. 2: https://www.drupal.org/u/tayzlor
  59. 3: http://www.mediacurrent.com/