[Closed] Form submits blank in Safari

[Author]

Posts

[matthewL-7]

Hi

I only seem to be experiencing this issue in Safari but I have had others report in other browsers I believe.

When a form is submitted it just goes blank and doesn't submit the data.

This is something to do with Cloudflare as if I disable this entirely it works.

Any ideas what I need to disabled magnification on or caching on?

You can see a form here - hidden link and try to test yourself you may not get the issue though if the page bypasses Cloudflare (sometimes it does on occasion).

I did get given this link - https://toolset.com/documentation/programmer-reference/toolset-resource-directories-for-cdn-upload/

However when I went on my server to follow the path for Forms Resources I noticed it didn't exist. So I think the document is out of date.

At the moment I have the following page rule setup on Cloudflare:
"hidden link"
Disable: Performance.
(This turns off: Auto minify, rocket loader, mirage and polish.)

[Christian Cox]

Hi, I've asked the documentation team to take a look at that CDN document, as you mentioned it contains some references to non-existent directories so I suspect it needs a general review from the developers. The information there is intended for use when uploading resources to the CDN for faster delivery to your site Users.

Apart from delivery of those assets, some performance optimization processes on CDNs and others provided by themes and 3rd-party plugins will concatenate, minify, and otherwise obfuscate JavaScript files for performance enhancement. As a general rule, we recommend you exclude all Toolset files from JS minification/compilation/obfuscation routines. However, we have found that the following file MUST be excluded from those routines, without exception:
- /wp-content/plugins/types/vendor/toolset/toolset-common/visual-editor/res/js/codemirror/lib/codemirror.js

If you're using Forms, these files must be excluded as well:
- /wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/js/validation.js
- /wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/js/conditional.js
- /wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/js/recaptcha-v2/api.js

So first, I would check to be sure these files are not minified/compiled/obfuscated, or otherwise "optimized" by a 3rd-party process. If that doesn't solve the problem, we can take another look.

[matthewL-7]

Hmm still having the same issue.

I have added the following page rules, I disabled virtually everything apart from caching on these files.

Any other ideas that could be causing the issues?

[Christian Cox]

Okay I'm running some tests now and I will give you an update shortly.

[Christian Cox]

Hello again, I have run several tests but I have been unable to replicate any problem in the registration flow on Safari / Mac OS 11.1 (all up-to-date, latest Big Sur). In short, I was not able to reproduce the blank response screen in any one of six tests. First I created one account successfully, taking my time and watching the network activity. Then I proceeded to create five more accounts in rapid succession. Each time I submitted the form, a spinner appeared as expected, indicating the AJAX query was in process. After a few moments, the page contents were switched out programmatically and the Form was replaced with some text that follows, as expected:
"Thank you, your account has been now created..." etc.

I also received an automatic email notification for each of these registrations at the email address I used in the registration form. So as far as the registration workflow goes, I don't see any immediate issues. I'm attaching a screenshot here so you can verify the things I've noticed so far.

Without being able to reproduce the problem successfully for analysis, I'm stuck. I think we could try a few other things to learn more about the error(s):
- Turn on server logs temporarily and try to capture info about the server-side error that results in a failed registration.
- Review any existing logs for more information about recent errors.
- Whenever you run a test registration, be sure the browser's JavaScript console is open and set to preserve log contents. This will keep the logs available for review even after the page changes. Share the logs produced during a failed registration in your next reply, and I will provide feedback.
- Ask for more details from site visitors who experienced a problem. Were they using a specific device of some kind? Were they eventually able to register, like by refreshing the page?

[matthewL-7]

Very strange I can't seem to see the issue any more.

The only thing I can think is maybe Cloudflare took a while to propagate the changes I setup, they usually say this takes 30 seconds but I have noticed in the past that sometimes it takes longer but usually minutes, not like 24 hours.

I will keep an eye on it over the next few days but fingers crossed it looks like the changes we discussed may have fixed the issues. 😊

[Christian Cox]

Great, I'll stand by for your update.