Page MenuHomePhorge
Create Task
Maniphest T183

Produce error pages for server downtimes
Open, NormalPublic
Actions

Description

Filed as a support ticket poked for this.

Users would like a slightly better help page for when there are operations issues like 502/3s.

While the ticket requested more details on the issue, it's not really possible to throw up the exact error as the logs often don't show it. Then there's the issue of getting that log entry.

So we'll keep a generic "server went away" or something like that. Should be simple, but with a bit of colour and a bit of text. Might be worth throwing a link to the blog or social media in there as well to keep people up to date?

Related Objects

Event Timeline

lewiscawte triaged this task as Normal priority.Mar 14 2017, 2:24 AM
lewiscawte created this task.
lewiscawte added projects: Restricted Project, Design.

Thinking about it, we could do with a better 404 and 403 error page.

Error pages are almost wasted talent, as we don't really want people to see them, but alas, sometimes they do, and they shouldn't be terrible.

SamanthaNguyen mentioned this in T185: Improve current client error 404/403 pages.Mar 14 2017, 7:50 AM
SamanthaNguyen added a project: I18n.
In T183#2639, @lewiscawte wrote:

Thinking about it, we could do with a better 404 and 403 error page.

Error pages are almost wasted talent, as we don't really want people to see them, but alas, sometimes they do, and they shouldn't be terrible.

Since 403 and 404 errors are different, I've split them off to T185.

We'll also want to translate the 502/503s in as many languages as possible before deployment since we have a multilingual audience.