Get rid of messageQuit in frontend

Because I really don’t like the idea of users seeing modx aborting with sql-errors, I committed a change of document.parser.inc.php to my branch which redirects users to default error page in case a ’messageQuit’ occurs. Of course, manager users will still see this messages since it’s useful for debugging.

Any opinions?

Sounds like a long-overdue, and wonderful idea to me. +1

Excellent idea.

So long as errors are logged in the db then all is well...

And maybe do something about the amazingly useless error messages in the Manager’s system alerts/system events? Nice to know that there is an unexpected whatever, or "Creating default object from empty value" ( ), but most of my modules consist of several files, and there is no clue here as to where the error ocurrs. A raw PHP or Javascript error would be more informative.

@Mark: They weren’t before, but they are now.
@Susan: Do you have any example, I haven’t seen such errors yet... Where do they occur?

Sorry, that was really off-topic, I’m just developing a complex module right now and it is really annoying me.

I’ll have a look at the module error logging, too...

BTW: I’m surprised, your branch works with Green Theme Mine doesn’t (fresh copy from trunk)...

I just installed the latest svn copy on my new site, and other than a small glitch in the installation I’m doing fine so far... http://www.loripsum.co.uk (willl be a site showcase).