[MGNLUI-1846] Clarify the error message shown on the 500 - internal error page Created: 17/Jul/13  Updated: 16/Aug/13  Resolved: 22/Jul/13

Status: Closed
Project: Magnolia UI
Component/s: app framework, user interaction
Affects Version/s: None
Fix Version/s: 5.1

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File error-message-v2.png     PNG File error-message.png    
Issue Links:
relation
is related to MGNLUI-1180 Customize 500 page when a ServletExce... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

I'd like to improve the current error message shown on the 500 page. First, it's unclear what an "application" is in that context. Second, I think we should improve it also to make it better understandable to non-technical users.

My suggestion is:

Whoops!

The server has encountered an internal error.

[Click here to attempt to recover by restarting the user interface].

We apologize for any inconvenience caused.

If you keep experiencing difficulties, please contact your system administrator.
Make sure you send along the stack trace below to help in tracking down the cause of this.

[Click here to view the error's stack trace].


 Comments   
Comment by Andreas Weder [ 17/Jul/13 ]

Linking a previous issue showing the message, which probably didn't go through acceptance. Or if it did, my acceptance was quicker than required

Comment by Mikaël Geljić [ 20/Jul/13 ]

Attached as suggested, although I think it's a bit too verbose then (esp. the main actionable item). Here's my proposal:

Whoops!

The server has encountered an internal error.

[Click here to attempt to recover]

If you keep experiencing difficulties, please contact your system administrator.
Make sure to send along the stack trace below.

We apologize for any inconvenience caused.

[Click here to show the error's stack trace]

Comment by Andreas Weder [ 22/Jul/13 ]

You're right, it feels too wordy. I'd still like to see the apology after the first section to better group the rest of the message together with the last action. And I suggest we add "from this" after "to recover", and to use "you" instead of "to" in the last sentence. So:

    Whoops!

    The server has encountered an internal error.

    [Click here to attempt to recover from this]

    We apologize for any inconvenience caused.

    If you keep experiencing difficulties, please contact your system administrator.
    Make sure you send along the stack trace below.

    [Click here to show the error's stack trace]
Comment by Andreas Weder [ 22/Jul/13 ]

Thanks, looking good now.

Generated at Mon Feb 12 08:50:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.