I recently had to update Gravity Forms on a client site due to a security vulnerability within this product, and it appears in the recent releases, GF removed the form submit event? Why would you opt to remove an extremely common and useful event that’s found on almost every form? We had 3rd party tracking scripts that were added via GTM that no longer work as well as internal custom developed scripts. It seems Gravity Forms is pushing for the use of the php hooks, which will work with rewriting of the internal logic. But the 3rd party scripts are JS based. And they are universal to work with all forms. And now they work with all forms except Gravity Forms, requiring a custom solution for only this product. It will require 2 points of code instead of one. Clients already pay for this product, and now it’s less flexible than others.
See the following:
The issue with the replacement that’s been added (gform/submission/pre_submission) is that it doesn’t account for form validation. If you want to do something on successful form submission, your only choice appears to be the php filter. Which again, causes an inconsistency for any 3rd party scripts that now have to manage their logic in two places, one of which, they usually don’t have access to.
The issue with the replacement that’s been added (gform/submission/pre_submission) is that it doesn’t account for form validation.
To be fair, the default submit event never accounted for validation either.
You can suggest adding support for live front-end validation directly to the product management team for consideration when planning future releases on the Gravity Forms product roadmap page.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.