dorota (dstroy) wrote in suggestions,
suggestions better error message than "Internal Server Error"

Title better error message than "Internal Server Error"

Short, concise description of the idea
if possible, please make error message recieved when accessing journals that are in bad states as "friendly" as the error message that is recieved for - The current 500 Internal Server Error seems to scare the crap out of newbies.

Full description of the idea
There's a cluster down at the moment - unfortunately, my journal is on it, so anyone trying to access my journal is getting errors. I have a lot of very very newbie (grandmothers and so on) family members who read my journal, and it would be helpful if the error messages that can be controlled could be all made a bit less technical and a bit less scary to folks like them.

when they access my journal via: (which is how I bookmarked their machines, so that they would get the "faster service" that my paid member status supposedly offers) when the server is having problems they see this:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

But had they tried to access the same journal via
They would have been seeing a much friendlier message that reads:
We're currently experiencing some technical difficulties. Please try again in a few moments.

You may be receiving this error as a result from maintenance or other site problems; please refer to to keep updated on the status of the site.
Is there any way to make the error page that comes up for the paiduser url as friendly as the one that comes up for free users?
My newbie family members have been calling me all weekend complaining that "they must have broken it or done something wrong" etc etc. The friendlier message would have alleviated a lot of their concerns.

An ordered list of benefits

  • -clearer error message
    -less panic for visitors to journals that are currently down
  • An ordered list of problems/issues involved

  • I think the only drawback is if it's a page that cant be controlled, but I suspect it's something that can be altered.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • um...find 500 Internal Error Message that comes up for this error and change text to be similar to more friendly "Sorry site is having technical difficulties" error message that comes up for the free users?
  • Tags: site copy, § implemented differently
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded