Saving Forms Seriously Broken
-
Message “Something went wrong while saving your form – Please try again”, seems to randomly appear on some forms (not all) since the last plugin update. Even a form that has not been modified has this problem if just open it and then try to save (update button) it. Trying again changes nothing… condition is persistent. Some new forms seem to have this problem once they have been edited (adding or changing fields, especially if changing e-mail submission text or changing PayPal action from Sandbox to Live). This is a crippling problem… making forminator completely unusable… please advise.
-
Hello @jayunger ,
I’m sorry about this issue.
I have been testing formulator since the last update was released and I haven’t seen any issues like that.
Can you try reinstalling plugin? Maybe something was corrupted during the updated.
kind regards,
KasiaPlease note I can update and save some forms…. but others (seemingly randomly) are having this problem.
Three quick questions:
(1) Will reinstalling the plugin have any effect on existing forms. I can’t afford to lose all my forms and submission information.
(2) What might cause such an error message as described above…. is it possible that my database is somehow corrupted. What can I do to correct this.
(3) I tried exporting and then importing some of the forms that don’t save properly. I can’t seem to make this work… when I try to import and exported form and past the export data into the text box… nothing seems to happen.
I just retried Import / Export and I confirmed that on the forms that I cannot successfully save I can also not import … while forms that I can save I can import.
Hi @jayunger
Could you check the browser console when this issue happens?
And check if there is any JavaScript error?
https://developer.mozilla.org/en-US/docs/Tools/Browser_ConsoleAlso, enable the debug mode following this guide:
https://premium.wpmudev.org/blog/debugging-wordpress-how-to-use-wp_debug/As soon as the issue return, check if any debug.log was generated on the wp-content folder.
You can upload the file on the google drive and share the link, or copy and paste the log if is not too big.
let us know the result you got.
Best Regards
Patrick FreitasAs requested I did an update of a form that fails to save and found JavaScript errors in the web console copied below. Running a form that does not fails to update does not generate any JavaScript errors.
————————————-
`Error: Request failed with status code 403
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:1
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
m https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:1
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:1
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:1
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
promise callback*r.prototype.request https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
e https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
exports https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:1
value https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
value https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
setTimeout handler*value https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
value https://ranachquafoundation.org/wp-content/plugins/forminator/assets/js/form-scripts.js?ver=1.14.0:25
Vh https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:163
Uh https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:14
Xh https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:14
af https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:14
Yh https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:164
nd https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:15
nc https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:15
Of https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:38
Ac https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:39
unstable_runWithPriority https://ranachquafoundation.org/wp-includes/js/dist/vendor/react.min.js?ver=16.9.0:26
Ma https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:52
Be https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:119
xi https://ranachquafoundation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:39Upon further experimentation this has something to do with HTML content in the submission eMails. If I edit the submission eMail in an external editor and paste it into the forminator edit form page… then I can’t save the form. However, if I type the very same HTML into the forminator edit form page … then save works just fine. I can’t figure out why this difference should generate the error noted in my previous post…
Hi @jayunger
The 403 status is a HTTP (as in HTTP protocol) status that means “Forbidden” so basically it says that “this specific request is not allowed”.
What you found about HTML content also might be relevant. This all together makes me think that it might be related to some sort of security feature/plugin either on site or on server. I’ve experienced similar issues (though with different plugin and under different circumstances) with a WAF (Web Application Firewall) active on one of the hosts.
So I think it’s something worth checking:
– if you have any firewall or similar kind of “blocking/limiting” security plugin/feature enabled on site, try temporarily disabling it (for testing)
– try the same with server; if you don’t see any option of that kind in your hosting settings or you don’t know if there’s anything like that – please get in touch with your host and ask them.Best regards,
AdamHello @jayunger ,
We haven’t heard from you for some time now – it looks like you were able to solve this issue.
Please feel free to re-open this ticket if needed.
kind regards,
KasiaI have determined that the cause of this problem is almost certainly a failure in the code to correctly escape some character sequences in the HTML entered in content of submission eMails. Specifically if a substitution of a field surrounded by curly braces ( e.g. {fieldname} ) in HTML is adjacent to an HTML tag enclosed in angle brackets ( < > ) then the save fails…. If however a meaningless space is inserted between the HTML tag and the field substitution the save is successful.
Hi @jayunger
Thank you for updating it.
I tested this on my website, let me check if I got the correct step.
Edited my email template, and on the {all_fields}, I added <{all_fields}>
Saved, and tried to save the form, but it worked fine.
Let us know if we are missing anything.
Best Regards
Patrick Freitas
The topic ‘Saving Forms Seriously Broken’ is closed to new replies.