You are here

Home » API reference » Flickr 7

README.txt in Flickr 7

Same filename in this branch
  1. 7 README.txt
  2. 7 filter/README.txt
  3. 7 block/README.txt
  4. 7 sets/README.txt
  5. 7 field/README.txt
  6. 7 cachewarmer/README.txt
  7. 7 feeds/README.txt
  8. 7 style/README.txt
  9. 7 tags/README.txt
The content of this file is based on the online documentation that can be found
at https://www.drupal.org/node/2490126. It is recommended to read it there.

Rebuilds the page cache after cron runs for selected content types also known as
cache warming. It avoids long page loads for the first visitor after a cron run.
See https://www.drupal.org/node/1576686/. Feel free to use the method there
instead of this sub-module. Either way works but don't use them together.

The server virtually visits all nodes of selected content types to ensure the
cache of these pages is rebuild after a cron run to avoid long page loads for a
real visitor. It can be limited to selected content types at
admin/config/media/flickr. The connection method automatically falls back to
cURL if stream_socket_client fails or is not available. Note that it uses the
HEAD method where the server MUST NOT return a message-body in the response.
Drupal will rebuild the full page's cache anyway.

Set the 'Minimum cache lifetime' to 'none' at
admin/config/development/performance.

It is recommended to set the cron interval to something sensible. By default it
is set to 3 hours at admin/config/system/cron. For many cases 'once a day' or
even 'once a week' is more than enough. New or edited content will refresh
anyway after hitting the 'Save' button.

File

cachewarmer/README.txt
View source 
  1. The content of this file is based on the online documentation that can be found

  2. at https://www.drupal.org/node/2490126. It is recommended to read it there.

  3. 

  4. Rebuilds the page cache after cron runs for selected content types also known as

  5. cache warming. It avoids long page loads for the first visitor after a cron run.

  6. See https://www.drupal.org/node/1576686/. Feel free to use the method there

  7. instead of this sub-module. Either way works but don't use them together.

  8. 

  9. The server virtually visits all nodes of selected content types to ensure the

  10. cache of these pages is rebuild after a cron run to avoid long page loads for a

  11. real visitor. It can be limited to selected content types at

  12. admin/config/media/flickr. The connection method automatically falls back to

  13. cURL if stream_socket_client fails or is not available. Note that it uses the

  14. HEAD method where the server MUST NOT return a message-body in the response.

  15. Drupal will rebuild the full page's cache anyway.

  16. 

  17. Set the 'Minimum cache lifetime' to 'none' at

  18. admin/config/development/performance.

  19. 

  20. It is recommended to set the cron interval to something sensible. By default it

  21. is set to 3 hours at admin/config/system/cron. For many cases 'once a day' or

  22. even 'once a week' is more than enough. New or edited content will refresh

  23. anyway after hitting the 'Save' button.