Webform keeps showing confirmation message after reload with redirect target "Confirmation page"

Created on 27 February 2021, almost 4 years ago
Updated 24 February 2023, almost 2 years ago

Problem/Motivation

After the webform has been submitted via AJAX with confirmation message, the confirmation message never goes away for the session on that webform.
If the webform is used on several pages via block for example, the webform block on all pages shows the confirmation message instead of the form.

Steps to reproduce

  1. Enable "AJAX Mode" and "Confirmation page" (important! The issue doesn't appear for "No redirect" option!) in the webform settings
  2. Use the form in a block (unsure if the same happens for webform pages yet)
  3. Submit a webform and see the confirmation message
  4. Switch to a different page with the same block - you still see the same confirmation message instead of the form

Proposed resolution

Reset the form after the confirmation message was shown once.

Remaining tasks

Check if this only happens for webform blocks
Check if this is caused by webform_ajax at all or if it's webform default behaviour / bug
Decide where and how to solve

User interface changes

API changes

None

Data model changes

πŸ› Bug report
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΈπŸ‡°Slovakia lubwn

    This exactly happened to me as well. I set the confirmation message to "no redirect" on webform block setting instead of webform form setting.

    I just switched "Confirmation message" in webform block setting to "Display as configured in the webform" and in webform settings page under Form settings -> Redirect location -> No redirect (reload current page) and it fixed the problem.

    So basicly nothing changed from user-perspective but somehow it fixed the problem.

Production build 0.71.5 2024