Add nicer error messages for specific conditions

[mtneug]

It would be nice to have specific error messages for some error conditions. E.g. if a user has no write access to the event, the following is shown:

A less technical error message should be shown instead of this generic error.

[Arnei]

I thought about this a bit and am unsure how to go forward with this. Specifically, what would be the most useful to users?

For example, we could move the technical error messages to the web console, where technical people will know to look for them. A professor who is trying to edit a video through their LMS will not care about that. But the tech support the professor will be contacting about their problem might find the technical error message useful.

Or would you like to keep the technical error messages, but reword them? So instead of "Status 403: No write access to this event" should this rather say "You are not allowed to edit this video"? And then do that for all the more or less common errors?

[mtneug]

I guess I wondered especially about this case. "You don't have access" should be rather clear and does not necessitate a technical error message. Yet I agree that having a technical error message in other scenarios could speed up support cases.

Maybe a path forward would be to handle a couple of common error cases with specific messages instead of the generic "critical error" wording. The technical error message could still be included, but may be greyed out / hidden to be less prominent.