Latest v1.5 bug (fix immediately please)

Hey @recveri
Thanks for your support and bug report. I can confirm that it’s a new bug (introduced with the new 1.5 release) and I have already fixed it on my working copy. I will release 1.5.1 version in the next few days, with this hotfix and a couple more updates that I am working on right now.

Meanwhile, if you want to fix this issue now on your installation, you can manually replace your wp-content/plugins/formality/dist/formality-public.js file with this fixed temporary version:
https://formality.dev/download/temp/formality-public.js

Let me know if it works as expected

Cheers,
Michele

Thank you very much for fixing this promptly. Yes, copying the provided JS to the folder wp-content/plugins/formality/dist/scripts/ fixed this issue.

Just an additional note that we have been anxiously waiting for recaptcha support and input type=date which is now supported by most browsers.

Thanks again.

@recveri Thank you again for your bug report. I have just published a new Formality version (v1.5.1) with this bug fixed.

Time/date field is in our plans, with a custom interface/datepicker (not sure if in a new “pro” version).

Recaptcha support is not a complex implementation but is not a priority now.
I haven’t received any reports yet about spams from our forms (Formality comes with a built-in antispam authentication)
Let me know if you receive spam with some informations about your installation (hosting/web address/etc).

Cheers,
Michele