Does setting a cacheable false on block invalidate full page cache for entire page?

Question

I have heard this but I cannot confirm it. Does anyone know?

Cladiuss · Accepted Answer · 2019-10-02 08:34:03Z

9

It is true, you can see it mentioned the Dev Docs too if you want extra confirmation :

To create an uncacheable page, mark any block on that page as uncacheable in the layout using cacheable="false".

You can see that on this page.

Cladiuss

1,2731 gold badge14 silver badges27 bronze badges

answered Mar 6, 2017 at 17:25

Ben Crook

15.7k4 gold badges52 silver badges105 bronze badges

So should this situation be avoided at all costs?
– LM_Fielding
Commented Mar 7, 2017 at 9:55
1

@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.
– Ben Crook
Commented Mar 8, 2017 at 9:49
I'm aware of hole punching methods, but thank you for the great tip! That is the reason I'm asking.
– LM_Fielding
Commented Mar 8, 2017 at 12:31

Add a comment |

Community · Accepted Answer · 2017-04-13 12:54:58Z

1

Yes it does. Full page cache will not be used on that page. But block cache and the rest works.

CommunityBot

1

answered Mar 6, 2017 at 17:25

Daniel Ifrim

3,4342 gold badges23 silver badges36 bronze badges

1

Of note, FPC is often responsible for the majority of caching performance gains, so thinking 'oh I'm just disabling one cache out of like 12' is usually a bad idea.
– siliconrockstar
Commented Feb 28, 2019 at 21:58

Add a comment |

2 Answers 2