Confirmation page gets cached with settings handler

Created on 9 February 2023, almost 2 years ago
Updated 26 May 2023, over 1 year ago

Problem/Motivation

Steps to reproduce

I had a form and the confirmation page message changed depending on the results. I used a settings handler to manage this depending on some conditions.

However, the confirmation page was cached (by internal page cache I believe)

So the message would stay the same between different submissions and some people would see the wrong message.

Proposed resolution

I've got round this by altering the route for all submissions. But I think the handers themselves should change the caching of the confirmation page if they alter its content.

It may even be that if a settings handler is defined we should not cache the confirmation page.

This is similar to https://www.drupal.org/project/webform/issues/2892854 β†’ but didn't involve tokens.

πŸ› Bug report
Status

Closed: cannot reproduce

Version

6.1

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom JeremyFrench

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024