Display Error Message Issues to User and log exceptions

[agarwali]

We need to start thinking about how to display error messages to users also making sure it's accessible from Sarah's presentation and how it is recorded in the logs.

e.g. we are catching exceptions and printing them but we should be logging them. Also, certain query functions like GalleryQueries.get returns none when it doesn't work but we should also be showing an appropriate error message to the user or redirect them to a certain URL.

[Jessonsotoventura]

Agreed

Showing errors

I was thinking that we need two separate ways of showing errors, since I think we have to
separate kinds of errors: those that cause and action to fail (like submit) and those that fail due to the source not existing (trying to view a gallery with gid = 10, when that does not exist)
In the case of the former (let's say it is the dropzone page) the page that fails has current data that exists, so I think the best way to handle that would be to throw a flash message with the error.
In the case of the latter (let's say going to gallery/submission/40) the page displayed will be only the skeleton. I think showing an error message on a page like this is pointless. I think we should have a page similar to similar to this where we replace the text with the reason it does not exits. Not having a gallery with gid = 40 is similar in my mind to a page not existing. Thoughts?

Logging

Yes, we need to figure out logging. ** I don't think that on any of our systems we have a good logging system. Do you have suggestions for this**? I have not looked into logging much.