Closed (works as designed)
Project:
Printer, email and PDF versions
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Feb 2013 at 05:04 UTC
Updated:
12 Mar 2013 at 13:58 UTC
Comments
Comment #1
tripper54 commentedComment #2
jcnventuraThere's a reason why the caching mechanism is like this.. Simply put, there's no way to be sure that the cache is valid for non-content pages, as they get generated on the spot. The current behavior of the system is to delete the cached file when the node is updated to force a re-generation, and this is not possible with non-content pages.
See http://drupal.org/node/516466#comment-6390678 for a brief description of the caching mechanism.