Hello again,
After reading further on the forum, I suspect I am not the only one with these problems with Email Notifications Conditions. Please see the following question:
https://wordpress.org/support/topic/email-notifications-with-conditions/
I suspect that because of this, new problems have arisen since the 1.17.2 update with those Email Notifications Conditions.
-
This reply was modified 1 year, 8 months ago by alainmelsens.
Hi @alainmelsens
I hope you’re well today!
The best way to test that for us would be to just test your form. You can export such example form from plugin (it will not import submissions so no worries about that) – just set some fake e-mail addresses in notifications before exporting if you prefer not to share those.
To export the form simply click “Export” in menu under the “gear” icon next to the form in question on “Forminator -> Forms” page, then download the export file and put it on your Google Drive, Dropbox or similar account and post direct link to it in response here.
However, I’m suspecting the issue is related to options values here. Take a look, please, at the options of fields based on which these conditions are set. I suppose they may contain some uppercase and/or special characters.
If they do, then editing them to contain all lowercase and no special characters and then just updating conditions in notification settings should help for now.
Would you check it and let me know if you can confirm?
If this isn’t the case, then please share the form as explained above so we could test it.
Kind regards,
Adam
Hi Adam,
First of all, thank you very much for your quick and very interesting reply.
Indeed, it is strange that before the upgrade to version 1.17.2 it worked and after the upgrade it doesn’t work anymore.
But now you are also right that the fact was that I had indeed, before turning on the checkbox, set the value for it equal to the capital X. After changing to a lower case x the problem is now solved and the Email Notifications Conditions work again as before. This then means that this upgrade to version 1.17.2 did change these condition settings. Best to make a note of this to avoid this problem from happening again.
In any case the problem has been solved sooner than expected for which I would like to thank you.
This ticket may be closed.
Thanks again for your quick response! Really very professional support.