Default Form Configuration shows token errors

Created on 6 January 2025, 3 months ago

Problem/Motivation

I freshly installed Webforms on an existing site. During configuration, I installed Honeypot and went to Webforms Configuration -> Forms to enable the Honeypot integration. Upon trying to save, the following errors showed up at the top of the page:

Error message
Default preview page title is using the following invalid tokens: [webform:title].
Default confirmation message is using the following invalid tokens: [webform:title].

The defaults that I did not change are:

Default preview page title: [webform:title]: Preview
Default confirmation message: New submission added to [webform:title].

For some reason trying to save these settings causes the error. I cannot find what the correct tokens should be for these sections.

Steps to reproduce

  1. Install Webforms
  2. Go to Configuration -> Forms
  3. Leave defaults and attempt to save configuration

More Info

I am not using CDN libraries. I followed the instructions to install the libraries locally using composer which seems to have worked successfully.

Help Requested

Please let me know if I have done something wrong or missed a step to cause this. Otherwise, please advise if these tokens are incorrect and I should be using other tokens. I would like to maintain the intended functionality if possible. Otherwise, please let me know what my options are to fix this.

🐛 Bug report
Status

Active

Version

6.2

Component

Code

Created by

🇨🇦Canada ciesinsg

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

Comments & Activities

  • Issue created by @ciesinsg
  • 🇨🇦Canada ciesinsg

    Just posting an update. I switched to 6.3.0-alpha3 and this bug is no longer occurring on this alpha version. I actually don't even see either of the below fields in the settings:

    • Default preview page title
    • Default confirmation message

    With this version, I am now able to enable the Honey integration and save the settings without the previously mentioned errors coming up.

    It looks like this issue is specific to version 6.2.x.

Production build 0.71.5 2024