running Wordpress 6.7 on our site with GF 2.9.0.1 and all GF working correctly. Site (https://bookings.mwscouts.org/) auto updated GF to 2.9.0.4 late yesterday and now the GF do not display on any of the pages. Our other site (https://shop.mwscouts.org/) running same version of Wordpress, woo commerce and many of the same plugins (e.g. W3TC for caching) is displaying the GFs correctly on pages where they used.
Fortunately had copy of the 2.9.0.1 zip file which we could load onto main site and forms are displaying & working correctly again. So it would appear there is an issue with the 2.9.0.4 upgrade.
Since updating to 2.9.0.4, have you cleared the caches of any caching/optimization plugins/services the site could be using?
Caching and script optimization plugins (e.g. W3 Total Cache, WP Rocket, etc.) and services (e.g. host provided, Cloudflare and their Rocket Loader feature) have been known to cause issues like this. We recommend excluding pages that include forms from those features.
See the following page of the documentation for more details: FAQ on Cache and Script Optimizer Issues - Gravity Forms Documentation
If the issue isn’t caused by caching or optimization, the next step is to perform a conflict test, following the steps described here: Testing Theme/Plugin Conflict
Note that for a valid conflict test, a test must be done with only Gravity Forms enabled. All other plugins, including third-party add-ons for Gravity Forms, should be disabled, and a default WordPress theme without custom code should be used (e.g. Twenty Twenty-Four).
Yes all W3TC caches cleared including browser cache.
We do not use cloudflare or Rocket loader services.
Rolled GF back to 2.9.01 and everything works fine as before.
The site uses the Woocommerce Storefront Theme (up to date version).
Pages are built with the Wordpress Classic /Block editor; we do not use any 3rd party page builder.
We, too, are having an issue where the forms are no longer displaying on our site, but we are using Version 2.9.0 and are experiencing this problem. The affected pages were/are all set to not cache.
Are they also excluded from script optimization? If the site is using Cloudflare, is their Rocket Loader feature disabled?
On some of the forms when the submit button is clicked, we are now getting a “The link you followed has expired”
That’s a WordPress nonce validation error. That usually only happens if the page is cached and the nonce has expired.
Created a test site from the backup of the main site.
Deactivated the W3TC cache plugin (having purged all caches), cleared browser cache and still getting the “The link you followed has expired” error using 2.9.0.4 version of gravity forms plugin.
Then deactivated the GF plugin, no “The link you followed has expired” error.
Left GF plugin deactivated, re-activated W3TC caching and everything works fine.
Re-activated GF plugin and the “The link you followed has expired” error produced when the form is submitted.
Have you attempted running a complete conflict test using the steps outlined on this documentation page: Testing for a Theme/Plugin Conflict?
Yes. Tested themes, and all plugins now, the result of which we have identified that the linked expired error only occurs when:
- a GF is attached to a woocommerce product using the Woocommerce Gravity Form Product Add-ons plugin by Element Stark (version 3.6.6 ) and
- the attached GF requires the user to be logged in the attached GF’s form settings.
Item 2 was only discovered in that we had 1 attached form that did work and when we looked at what was different we found that it did not have the “user must be logged in” box in the GF form settings checked. We unchecked this option in the other attached forms and the “linked expired” error no longer occurred.
As an additional part of testing, we then put the effected GFs with the “user must be Logged in” checked in the form settings into standard wordpress pages and then complete the forms to see if the “linked expired error” would occur. When we did this there is no linked expired error.
So, it looks like the error is only produced by the combination of the following two things:
- “user must be Logged in” checked in the GF’s form settings; and
- The GF is attached to a woocommerce product using Woocommerce Gravity Form Product Add-ons plugin by Element Stark (version 3.6.6 ) to displayed in the product page.
Prior to the update of GF to 2.9.0.* and Gravity Forms Product Add-ons for WooCommerce from 3.6.3 (our previous version) there was no occurrence of the “linked expired” error.
I recommend contacting the developer of the WooCommerce integration for support with this issue at WordPress.com
A lot of the front-end scripts, including the submit button and form submission handler, were updated in 2.9 to use plain JavaScript instead of jQuery, so they most likely need to update their integration for compatibility.