Email validation problem

The Google Forms plugin makes a call to wp_mail() when the mail confirmation is enabled. Are you receiving other mail from your site (comment notification, user registration, etc.)?

I received an email this morning saying the site was updated to WP 4.3. I have the auto update option enabled.

Any chance the emails are ending up in your spam? I get email every time someone fills out my Help and Support Request form.and that part of the code has not changed in a long time.

There’s been a misunderstanding so let me try to explain this again.

1. Emails arrive as they should. This is not my problem.

2. The email validation should show a warning when someone types in an ill formatted email address. And it should go away when the email address is properly formatted.

The problem I have is that the email validation warning is ALWAYS showing. It shows up when the page loads and I haven’t even started typing in the form yet. And if I fill in a proper email address it’s not hiding either.

Please look at the page I refered to in my first post.

You’re right, I wasn’t reading your question correctly.

It looks like two different things (plugins, themes – something) are defining the CSS for the error-message class. I would suggest adding a CSS prefix to your Google Form definitiion and then add the same CSS prefix to all of your Custom CSS classes.

The CSS prefix will prefix every CSS class with the prefix so if you are using some of the default CSS shipped with Google Forms, you may need to add new CSS rules for those classes using your prefix.

Sorry I didn’t understand much of that. How can css affect the validation? Isn’t it a script?

It worked in earlier versions. The site is one year old and it was now I noticed this new problem.

The CSS doesn’t affect the validation by itself, it is whether or not the validation message is visible or not. Google defines DIV elements to hold validation messages as part of the form and by default they are invisible (in CSS terms the display property is set to none). The validation process then makes the DIV elements visible either using jQuery or by changing the display property when the form is rendered again after submission.

Most of the CSS Google uses in their forms has a “ss-” prefix but the DIV elements which contain error messages do not. They use the very generic “error-message” CSS class. I have seen other plugins and themes define this same CSS class and add rules to change the appearance and visibility of DIV elements in other areas which ends up colliding with what is defined as part of the Google Form.

I cannot state with 100% certainty that is the problem you are having but that is my suspicion. I’ve seen it several times previously. The CSS prefix and suffix (I recommend prefix) option with the Google Forms plugin is a mechanism to ensure CSS collisions don’t happen. Defining a CSS prefix is a pretty simple way to see if this is the problem you are facing.