Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-29078

Varnish cache should be purged for changes to items in Landing Page blocks

    Details

      Description

      Same as EZP-28848, however for content rendered on landing pages after cache of blocks whre introduced in
      EZEE-1886 & EZEE-1896.

        Issue Links

          Activity

          Hide
          André Rømcke added a comment - - edited

          Merged: https://github.com/ezsystems/EzLandingPageFieldTypeBundle/commit/61d5c27765ddd658c5bd2d77bacb819c77ce2ec6

          QA: So this should in practice allow the newly introduced Landing Page block cache (in 1.12.1/1.12.1 released beginning of march) to be cleared not only when the landing pages is updated or ttl time runs out, but also when the block content item (aka "relation") itself being listed in the block is updated* as well.

          * When I say updated I mean re-published, or otherwise actions like meta update or delete happens on the given object directly. In the current patch, cache will not be expired if the related item is deleted in a subtrees delete (when item is not the tip of the tree). This would be improvment potential for later (potential way: expose a twig helper to help generate cache tags when rendering content items inline, or handle natively in Page controller or similar)

          Show
          André Rømcke added a comment - - edited Merged: https://github.com/ezsystems/EzLandingPageFieldTypeBundle/commit/61d5c27765ddd658c5bd2d77bacb819c77ce2ec6 QA: So this should in practice allow the newly introduced Landing Page block cache (in 1.12.1/1.12.1 released beginning of march) to be cleared not only when the landing pages is updated or ttl time runs out, but also when the block content item (aka "relation") itself being listed in the block is updated* as well. * When I say updated I mean re-published, or otherwise actions like meta update or delete happens on the given object directly. In the current patch, cache will not be expired if the related item is deleted in a subtrees delete (when item is not the tip of the tree) . This would be improvment potential for later (potential way: expose a twig helper to help generate cache tags when rendering content items inline, or handle natively in Page controller or similar)

            People

            • Assignee:
              Unassigned
              Reporter:
              André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: