Custom confirmations not working since 2022

Custom confirmations messages do not work.
There are hundreds of complaints about this if you Google it, many on this forum dating back to 2022. All them are unresolved and end up automatically closed or “please open a ticket” which does not help the community.

The problem is no matter what I do, I cannot get a custom confirmation message or page to appear after the submission. It is ALWAYS the default “Thanks for contacting us! We will get in touch with you shortly.” It happens on all forms. It happens with all confirmation methods. Even changing the default message on the form’s “Default confirmation message” doesn’t change it. It is using a hard-coded confirmation message.
It didn’t always have this problem.
There are a few common responses to this:

  1. We do not use Facebook plugins or the Facebook pixel.
  2. We do not have a plugin conflict.
  3. We are not using Akismet.
  4. This happens with or without conditional logic on the form confirmation.
  5. Neither the message confirmation or the redirect to a page confirmation method works.
    This is a widespread problem with Gravity Forms since at least 2022.

Has anyone figured out why this is happening?

These are the possible reasons why the default confirmation text used by new forms is used instead of the confirmations you have configured for the form:

  • The anti-spam honeypot is enabled in the form settings, and the submission failed honeypot validation. If the honeypot settings are configured to save the entry, a feature available since version 2.7, you should find it marked as spam in the entries area of the form. The default behaviour, which was maintained from earlier versions, is to abort without saving the entry.
  • Another anti-spam solution marked the submission as spam
  • The theme or another plugin is using the gform_confirmation filter, and returned an invalid value

You can confirm the cause by testing with logging enabled:

Again, as I stated - this s a Gravity Forms problem - not a spam problem.

  1. There are no other anti-spam solutions installed or active.
  2. The honeypot is not enabled on any form
  3. No messages are being marked as spam. All forms are otherwise working as expected, delivering all messages and nothing is being flagged.
    There is no other plugin or theme using the gform_confirmation filter. This was broken after an update to Gravity Forms.

I made a simple test form with 1 radio button field and submitted it using the PREVIEW of the form. It still has the problem. I had logging enabled during this test. Here’s the log:

2024-10-10 12:51:51.370567 - DEBUG --> GFCommon::send_email(): Result from wp_mail(): 1 
2024-10-10 12:51:51.370671 - DEBUG --> GFCommon::send_email(): WordPress successfully passed the notification email (#67082f0c84ca8 - Admin Notification) for entry #2184 to the sending server. 
2024-10-10 12:51:51.370714 - DEBUG --> GFCommon::send_email(): The WordPress phpmailer_init hook has been detected, usually used by SMTP plugins. It can alter the email setup/content or sending server, and impact the notification deliverability. 
2024-10-10 12:51:51.372028 - DEBUG --> GFCommon::send_notifications(): Sending notifications for entry (#2184) completed in 0.476076 seconds. 
2024-10-10 12:51:51.372118 - DEBUG --> GFFormDisplay::handle_confirmation(): Preparing confirmation (#67082f0c85809 - Default Confirmation). 
2024-10-10 12:51:51.372203 - DEBUG --> GFFormDisplay::handle_confirmation(): Executing functions hooked to gform_confirmation. 
2024-10-10 12:51:51.372366 - DEBUG --> GFFormDisplay::handle_confirmation(): Completed gform_confirmation. 
2024-10-10 12:51:51.372410 - DEBUG --> GFFormDisplay::handle_confirmation(): Invalid confirmation; using default text instead. 
2024-10-10 12:51:51.372486 - DEBUG --> GFFormDisplay::handle_confirmation(): Confirmation to be used => <div id='gform_confirmation_wrapper_38' class='gform_confirmation_wrapper '><div id='gform_confirmation_message_38' class='gform_confirmation_message_38 gform_confirmation_message'>Thanks for contacting us! We will get in touch with you shortly.</div></div> 
2024-10-10 12:51:51.372530 - DEBUG --> GFFormDisplay::process_form(): Executing functions hooked to gform_after_submission. 
2024-10-10 12:51:51.373364 - DEBUG --> GFFormDisplay::process_form(): Completed gform_after_submission. 
2024-10-10 12:51:51.373437 - DEBUG --> GFFormDisplay::process_form(): Processing completed in 0.513723 seconds. 
2024-10-10 12:51:51.376177 - DEBUG --> Gravity_Forms\Gravity_Forms\Duplicate_Submissions\GF_Duplicate_Submissions_Handler::is_valid_submission(): form #38. entry #2184. 
2024-10-10 12:51:51.396208 - DEBUG --> Gravity_Forms\Gravity_Forms\Duplicate_Submissions\GF_Duplicate_Submissions_Handler::is_valid_submission(): form #38. entry #2184. 
2024-10-10 12:51:51.405004 - DEBUG --> GFFormDisplay::get_form(): Preparing form (#38) confirmation completed in 0.009488 seconds. 

None of the extensions logs have errors as there were no feeds triggered on this form.

Based on the logging, this is the issue on your site:

  • The theme or another plugin is using the gform_confirmation filter, and returned an invalid value

2024-10-10 12:51:51.372118 - DEBUG → GFFormDisplay::handle_confirmation(): Preparing confirmation (#67082f0c85809 - Default Confirmation).
2024-10-10 12:51:51.372203 - DEBUG → GFFormDisplay::handle_confirmation(): Executing functions hooked to gform_confirmation.
2024-10-10 12:51:51.372366 - DEBUG → GFFormDisplay::handle_confirmation(): Completed gform_confirmation.
2024-10-10 12:51:51.372410 - DEBUG → GFFormDisplay::handle_confirmation(): Invalid confirmation; using default text instead.
2024-10-10 12:51:51.372486 - DEBUG → GFFormDisplay::handle_confirmation(): Confirmation to be used =>

Thanks for contacting us! We will get in touch with you shortly.

Something on the site is using the gform_confirmation filter:
Executing functions hooked to gform_confirmation.

and the confirmation it provides is invalid, so the default is used instead:
Invalid confirmation; using default text instead.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.