Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Handling: Full page error message requires updated links and messaging #48

Open
densoutar opened this issue Jan 3, 2018 · 3 comments
Milestone

Comments

@densoutar
Copy link

densoutar commented Jan 3, 2018

The "We've Run Into a Problem" page contains links to allow the user to try the last action again, or to contact the admin. The links and messaging on it need to be updated as follows:

  • The contact e-mail currently provided is [email protected]. This needs to replaced with the contact e-mail for the actual database admin.
  • The try again link needs to allow the user to return to the previous page, so that they can submit the action again. If this can't be done, it should not be styled as a link.
  • This screen is meant for unanticipated errors, which is why it starts out with ""We're not sure why..."", yet a non-human readable error message is provided. This error message should not be displayed on this screen.

Note: This error page was generated by clicking "Send Link" while leaving all the fields blank on the Create New Account page.

screen shot 2017-12-12 at 11 48 46 am

@paradoxxjm
Copy link
Member

We need to make sure the admin email address is correct.

However, I disagree with the suggestion to remove the machine-readable error. In this case, for this type of system (i.e not consumer facing), we do want the user to email that error to the administrator

@paradoxxjm paradoxxjm added this to the ProjectClose milestone Feb 25, 2018
@densoutar
Copy link
Author

@paradoxxjm The email address in the screenshot was meant to be a placeholder; it should be replaced with the Climate Change Division's admin/technical support email.

If you're saying that humanising the machine-readable error is not high on the priority list, I reluctantly understand; otherwise—so as not to wrong-foot our non-developer users too much— consider this tweak for presenting unanticipated technical errors:

technical error

@paradoxxjm
Copy link
Member

Looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants