Cache is not invalidated when changing view

neferin12 · July 16, 2026, 11:36am

I deployed a test platform using the default docker swarm that came with the project template. Varnish is enabled and works.

The problem is, when a editor changes the view for a folder (or any other content type) the cache is not invalidated and old view is not shown until the user force refreshes.

Is there any way to automatically invalidate the varnish cache on view change? I was unable to find a configuration for it.

There also is an existing topic for it: Content view not purged in varnish cache when switching view , but due to its age and lack of answer i felt it was appropriate to open a new one.

yurj · July 16, 2026, 12:57pm

github.com/plone/plone.app.caching

src/plone/app/caching/configure.zcml

2a8d959ee


      
          <subscriber handler=".purge.purgeOnModified" />
          <subscriber handler=".purge.purgeOnMoved" />
          <subscriber handler=".purge.purgeOnRemoved" />
          <subscriber handler=".purge.purgeOnWorkflow" />

Purges are done on modification, moving, removing and workflow. In plone.app.content, changing a view:

github.com/plone/plone.app.content

src/plone/app/content/browser/selection.py

ae7fa5793


      
          @property
          def vocab(self):
              return self.context.getAvailableLayouts()
          
          @property
          def selectedLayout(self):
              if not self.context_state.is_default_page():
                  return self.context.getLayout()
              return ""
          
          def selectViewTemplate(self):
              templateId = self.request.get("templateId")
          
              if self.isValidTemplate(templateId):
                  self.context.setLayout(templateId)
          
              self.request.response.redirect(self.context.absolute_url() + "/view")
          
          @property
          def action_url(self):
              return f"{self.context_state.object_url():s}/select_default_view"

calls setLayout:

github.com/plone/Products.CMFDynamicViewFTI

src/Products/CMFDynamicViewFTI/browserdefault.py

a4783baf0


      
              else:
                  if objectId is not None:
                      self.manage_addProperty("default_page", objectId, "string")
              if new_page != old_page:
                  if new_page is not None:
                      new_page.reindexObject(["is_default_page"])
                  if old_page is not None:
                      old_page.reindexObject(["is_default_page"])
          
          @security.protected(ModifyViewTemplate)
          def setLayout(self, layout):
              # Set the layout as the current view.
          
              # 'layout' should be one of the list returned by getAvailableLayouts(),
              # but it is not enforced. If a default page has been set with
              # setDefaultPage(), it is turned off by calling setDefaultPage(None).
              if not (layout and isinstance(layout, str)):
                  raise ValueError(
                      f"layout must be a non empty string, got {layout}({type(layout)})"
                  )

that finally call setDefaultPage that... reindex the object but don't call notify(ObjectModifiedEvent(obj)) with the modified event. I think it will work if you do so.

neferin12 · July 16, 2026, 2:15pm

Thank you very much for your answer! Unfortunately I do not quite understand. Should I notify the ObjectModifiedEventHandlers myself with the notify method? And if so, where should I do that? Can I myself listen for a view change?

yurj · July 23, 2026, 3:40pm

I think you've to test if changing Products/CMFDynamicViewFTI/browserdefault.py works. If it works, you can make a PR. Locally, you can do an add-on that overwrite the setLayout method.