Timeline for Does setting a cacheable false on block invalidate full page cache for entire page?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 2, 2019 at 8:34 | history | suggested | Cladiuss | CC BY-SA 4.0 |
Updated deprecated external link to newer version
|
| Oct 2, 2019 at 8:13 | review | Suggested edits | |||
| S Oct 2, 2019 at 8:34 | |||||
| Mar 8, 2017 at 12:31 | comment | added | LM_Fielding | I'm aware of hole punching methods, but thank you for the great tip! That is the reason I'm asking. | |
| Mar 8, 2017 at 9:49 | comment | added | Ben Crook | @LM_Fielding Unless you want to purposefully stop the whole page from being cached then yeah I would avoid. If you need to prevent one block from being cached take a look at hole punching methods. | |
| Mar 7, 2017 at 16:35 | vote | accept | LM_Fielding | ||
| Mar 7, 2017 at 9:55 | comment | added | LM_Fielding | So should this situation be avoided at all costs? | |
| Mar 6, 2017 at 17:25 | history | answered | Ben Crook | CC BY-SA 3.0 |