go to sections menu

Building a 404 page that helps fix bugs from blog The Technology blog and podcast

This is for the technology blog and podcast Commentary, articles, and podcasts

header picture for Ingegno theme

You are here: article commentary > Building a 404 page that helps fix bugs

Go to Homepage, contents or to navigation menu



Building a 404 page that helps fix bugs

I recently got an email through my Braille2000 site I’ve been talkng about for some time where people can learn and download documentation and audio regarding the Talking Edition of Braille2000.

The email included the error page in question, although it didn’t have to do that, but it became very helpful.

Here’s a copy of the email and I’ll talk about why I built the web page this way.

Hi Jared,

I was trying to download the RTF version of the documentation for using Braille 2000 with the self-voicing component. I visited this link.

http://jaredrimer.info/documents/Using_Braille2000_Voice.rtf

Here is the resulting text from the website.

We’re sorry! Something here went wrong. You came from /documents/Using_Braille2000_Voice.rtf and that may be wrong. Please 
contact us 
so we may fix it. This is not our intent, and we need to fix it.

Here is the page you came from that generated this error. Please let us know the page so that we may fix this quickly. It was http://jaredrimer.info/documents/index.php

Here is your browser. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.3673.166.157.230/documents/Using_Braille2000_Voice.rtf
It may not be needed, but it may help in certain circumstances.

Thanks for sending your report to us, so we can fix it!

There are aspects in the control panel I use called Cpanel. In it, there are things in place where I can get the URL the visitor was on, the browser if necessary, and lots of other things.

Here is how that page looks like without the email or the attached text.

We're sorry! Something here went wrong. You came from and that may be wrong. Please contact us so we may fix it. This is not our intent, and we need to fix it.

Here is the page you came from that generated this error. Please let us know the page so that we may fix this quickly. It was

Here is your browser. It may not be needed, but it may help in certain circumstances.

Thanks for sending your report to us, so we can fix it!

I put this in code because I don’t know if it’ll work otherwise, but you’ll see that these types of things are valuable.

Because I developed the 404 page this way, I was able to fix a URL which is vital for people to have and its in parts of the web site in other places too. The generic 404 page says:

Not Found
The requested URL was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

How helpful is this? Its not helpful to me, and I figure that if I can assist through the methods provided to me to get the info, it’ll help out.

Some people may not know where they came from, or what they were trying to do. Seeing this in an email assisted me in fixing the error quickly, and finding out why it occurred to begin with. It started locally, and so if I refresh the pages again, it’ll happen again so I fixed it there too.

Thats why I made the error page this way, it just saved hours of work I fixed in 5 minutes.

Thoughts about error pages and their value or non-value aspect?

I’d love to hear from you. Let me know what you think of this topic because I thought this was something that could easily be implemented and was used during beta.

The Braille Transcribing as a blind person web page is the page where this 404 page is on, and I’ve got similar pages for MENVI too where there is a set of links back to the main pages. I didn’t do this there, even though I really should, but the pages are more static there and bugs were fixed during development.

Thanks for reading!


Informazioni sull'articolo

Building a 404 page that helps fix bugs was released on February 4, 2020 at 3:00 pm by tech in article commentary.
Last modified: February 4, 2020.


Comments (0)

No comments yet.

Leave a comment

Message form







go to sections menu


navigation menu

go to sections menu