Many Broken Items | Gravity Forms 2.9.0 [RESOLVED]

Get Help
, , , , ,
1

Good Day,

Gravity Forms 2.9.0 has been a mess for us.

For example, many of the GF filters issued for replacing and/or hiding button spinners no longer work. This has rendered our forms completely unusable plus visitors cannot submit our forms.

Two things:

  1. How can we downgrade Gravity Forms to its previous revision, 2.8.18, without pulling up one of our site back-ups? You guys should carefully evaluate and implement a new system for rolling back plugin revisions same as offered by Rank Math SEO. Their rollback system is flawless and temporarily helps correct issues that can be further debugged and fixed.

  2. We noticed that Gravity Forms 2.9.0.1 – which may fix those issues – is in work. When can we expect the revision to be released?

Thank you!

2

More info:

The following filters, etc. do not work with GF 2.9.0:

3

The gform_review_page filter is working with Gravity Forms 2.9 on our test sites.

The product team are aware of the issue with the submit button code snippet. It will be fixed in 2.9.1. You can actually fix it now by updating the code snippet to use the approach found here: gform_submit_button - Gravity Forms Documentation

The Gravity Wiz code snippet for the spinner is not currently compatible with Gravity Forms 2.9. It is targetting an img element. Gravity Forms now uses a span element and CSS for the spinner. You’ll need to update the code snippet to target that instead, e.g.

.gform_wrapper.gravity-theme .gform-loader {
    display: none;
}
4

Thank you. Will review and fix whatever we can at our end.

BTW, we used that approach (both filters) and they don’t work at our end. For troubleshooting and to confirm, we disabled all plugins.

Also, please know GF 2.9.0 breaks or renders inop the following plugin: gAppointments. We’ve been using it for years with no issues until GG 2.9.0.

Cheers!

5

You’ll need to report that issue to the add-on developer. 2.9 beta and release candidate versions have been available for the past few months, so they’ve had time to test for compatibility with it.

6

Hey @richardw8k,

Thanks for your help. Issues fixed. We fixed our issues as follows:

  1. We applied the CSS Rule (new) you provided for hiding the spinner. Namely:
.gform_wrapper.gravity-theme .gform-loader {
    display: none;
}
  1. We applied the following filter (new) for the “Submit” button (as noted here):
add_filter( 'gform_submit_button', 'gf_change_submit_button_text', 10, 2 );
function gf_change_submit_button_text( $button, $form ) {
    $fragment = WP_HTML_Processor::create_fragment( $button );
    $fragment->next_token();
    $onclick = trim( (string) $fragment->get_attribute( 'onclick' ) );
    if ( ! empty( $onclick ) && substr( $onclick, - 1 ) !== ';' ) {
        $onclick .= ';';
    }
    $onclick .= " this.value='Sending...';";
    $fragment->set_attribute( 'onclick', $onclick );
 
    return $fragment->get_updated_html();
}

IMPORTANT: The other filter labeled “The following approach works with all versions of WordPress:” does not work with GF 2.9.0. Verified. You may want to look into this.

  1. We applied the following filter (new) for the “Next” button:
add_filter( 'gform_next_button', 'gf_change_next_button', 10, 2 );
function gf_change_next_button( $button, $form ) {
    $fragment = WP_HTML_Processor::create_fragment( $button );
    $fragment->next_token();
    $onclick = trim( (string) $fragment->get_attribute( 'onclick' ) );
    if ( ! empty( $onclick ) && substr( $onclick, - 1 ) !== ';' ) {
        $onclick .= ';';
    }
    $onclick .= " this.value='Sending...';";
    $fragment->set_attribute( 'onclick', $onclick );
 
    return $fragment->get_updated_html();
}

IMPORTANT: You may want to add the above to your documentation. Not listed.

Thanks for your help and the leads.

Cheers!

7

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