My bad, I just realized it has nothing to do with the preselected option. The problem comes from my options, that both have an empty value. I need the empty value to work for my confirmation email, yet when my option has an empty value, the form shows an error. Please help! 🙂
P.S. I guess it’s also probably related to the fact that no special characters can no longer be inserted in the values.
-
This reply was modified 4 years, 8 months ago by
wireofhope.
-
This reply was modified 4 years, 8 months ago by
wireofhope.
Hello @wireofhope !
Hope you’re having a good day and apologies for the inconvenience caused by the issue!
I tried to replicate this on my test site, with one of the options set to be preselected, however in my case the issue wasn’t there – even when leaving the field as is, the form submitted successfully.
Would you be able to share your form with us so we can test it further? Here’s how to share it using our contact form:
https://premium.wpmudev.org/contact/#i-have-a-different-question and the template below:
NOTE: Don’t change selected topic in the dropdown, just leave it at “I have a different question”.
Subject: “Attn: Pawel”
– Site URL
– The form export as attachment or a link to the export file on Google Drive, Dropbox etc.
– Link back to this thread for reference
– Any other relevant urls/info
Kind regards,
Pawel
Thanks for looking into it, but as I said in my previous message, this has actually nothing to do with the preselected option.
Since the update, I cannot insert any special characters in my value fields, and leaving it empty is what’s causing the error. I don’t know what to do right now I need a quick fix, can I go back to the previous version of the plugin?
Thank you.
P.S. Even capital letters are not accepted in my value fields right now :'(
-
This reply was modified 4 years, 8 months ago by
wireofhope.
Hi @wireofhope,
We have responded to your email, please check your inbox and we can continue the discussion there.
Cheers,
Predrag
Hello @wireofhope ,
I checked the status of this issue and it was fixed in 1.15.3 – please update the plugin to the latest version.
kind regards,
Kasia