3

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

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.

3
  • So should this situation be avoided at all costs? Mar 7 '17 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
    Mar 8 '17 at 9:49
  • I'm aware of hole punching methods, but thank you for the great tip! That is the reason I'm asking. Mar 8 '17 at 12:31
1

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

Block with Cachable=false not rendered on product view page

1
  • 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. Feb 28 '19 at 21:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.