Thanks for the heads up on this! Will log this into our issue tracker By the way, since 1.4 is pretty near around the corner, we'll fix this in 1.4 instead

Mark wrote:

By the way, since 1.4 is pretty near around the corner, we'll fix this in 1.4 instead

Awesome, I'm patient for this. I looked at the roadmap a few days ago and had to tell Randall that I was excited to see ES 1.4 nearing completion. Seeing videos set to complete was the most exciting part.

Hey Josh,

I have been reviewing this and this is actually not an incorrect message. The message in the "Note" area is actually the "tooltip" or help section which describes more about the field

The real error message is actually shown as you can see here, http://screencast.com/t/BIIyKIBS

The real error message is actually shown as you can see here, http://screencast.com/t/BIIyKIBS

You are correct, I missed that detail. Because the regular expression patterns are customizable to our own needs, I take it there is no easy way for a validation message to check what validation rule is being broken? For example if my validation rule does not allow special characters, could the note dynamically change or add extra text saying what regular expression rule is broken? While on my own ES installation I could just say "Does not allow special characters ect." there is a very good chance that many other EasySocial customers will run into the same problem. Especially with some folks using spaces in their name and using @ for their email address username. Just looking out for other ES folks.

Hm, but those are actually not validation messages instead they are tooltips and replacing the tooltips with validation messages are pretty confusing?

I agree that it could be confusing which is why I figured adding more text to it might be less confusing if the additional text is red. A better solution is making the tooltip message display the validation issue(s). The tooltip only displays when the validation fails, hence the only thing that can change with the tooltip is the error message when it does fail. Here's an example:



This method is less confusing to the user, and instructs the user on why they cannot proceed.