Gravity Forms AJAX spinner disappeared and no plugins/theme conflict

General Discussion
, ,
1

I updated plugins and the spinner icon is not showing anymore when submitting forms. I disabled several plugins and still was not working.

  • The image file exists
  • ajax is enabled
  • no plugins in conflict
  • no javascript errors
  • disabled cache to test
  • plugin was deactivated, deleted and installed again (we had to download it from your site as WP doesn’t update it properly)
  • tested from different computers / different browsers

I followed this guide {today} Merge Tags - Gravity Forms Documentation find conflicts:

  • form was tested in a test page without using the beaver builder, testing with ajax and without it
  • The page was excluded at Fastest Cache plugin and the minimize Css was removed. Also the plugin was later disabled but no results.
  • A new WP Theme Twenty Twenty Three was changed and still no spinner.
  • I deactivated all plugins and just left Gravity and nothing

A test was made to replace the spinner but it didn’t show (gform_ajax_spinner_url - Gravity Forms Documentation) (removed later)

This was tried without luck (removed later)
.gform_ajax_spinner {
display: inline-block !important;
visibility: visible !important;
width: 24px;
height: 24px;
}

2

I got a reply from Gravity and it worked by disabling the legacy markup in the test form:

The form showing on the URLs provided are currently using legacy markup. As a first step, please try disabling legacy markup for the form by unticking the setting at Form → Settings → Form Options → Enable legacy markup . This will cause the form to be styled with a newer theme. After doing so, please test again to see whether the spinner is rendered.

Regarding legacy markup, please also note from documentation About Legacy Markup:

⛔ Legacy markup is scheduled to be removed from Gravity Forms with the release of Gravity Forms 3.1. When deprecated, the forms will default to standard markup, operating as if the legacy mode setting has been disabled. This transition may introduce issues if your site has existing custom code that depends on the legacy markup structure.

We don’t have a firm timeline for version 3.1 yet. You can reference the Gravity Forms Changelog for our historical release dates which should help project some idea for when 3.1 may land.

Regards,

3

However, this only fixed the form in a test page I had, not the other forms. I thought it had to do with Beaver builder but disabled the plugin and the forms couldn’t even be submitted.

Any one has any ideas?

4

Well, it seems that Cache shouldn’t be enabled on the pages with forms. That’s unfortunate because in our case, those pages are the ones we need to be faster.