I’ve become a huge fan of all of the client side field validation processes (jQuery, prototype, etc.) that have emerged over the past few years. I think they lead to a better experience for the user and I’ve made it a habit on all of my projects to use this type of process.

What frustrates me though is my inability have control over all the messages that EE might generate. Yes I can style them to my hearts content, but I’m still left with the errors posting to a different page. Unfortunately client side field validation only goes so far. I can’t use it to address all errors the system may generate after evaluating a users submission.

I’m wondering how feasible it would be to provide a means by which the error messages could be directed to the template that contains the form that attempted to submit content?

Thanks for taking the time to read this request.

It is only half-true that you can style these messages as you please because you cannot use any EE tags. This is what I find really frustrating about error messages in EE. Why I cannot use global variables, such as {site_name}, or embeds or path variables?
Such restrictions does not seem to have any sense.

I think that provided the five required variables: {title} {meta_refresh} {heading} {content} {link} in error message are retained, the use of EE tags should be allowed.

The hook to allow EE error messages to be displayed in templates also would be handy.