404 Error - The Page Cannot be FoundGet Web Design Tips and Tricks on mps-web-design.com. 404 Error - The Page Cannot be Found topic will increase your understanding on Web Design Tips and Tricks. We at mps-web-design.com only provide news, articles, information in Web Design Tips and Tricks. Web Design Tips and Tricks at mps-web-design.com provides the most up to date news and articles. If you have questions please do not hesitate to contact us.
A "404 Error" happens when the web server you are on cannot find the page that you requested. This type of error is quite common and is seen all over the place. 404 Errors can be caused by many different problems, though generally they are caused by either dead links, or errors in the websites coding. Dead links often occur when a webmaster puts external links on his website, then the website he is referring to changes, moves, or no longer exists. Coding errors on the other hand can happen all over the place! Quite often webmasters neglect to check their links as they are making them, this means that there could be a spelling mistake in the URL, a missing slash or pretty much any typing error you could think of. It's good practice to check all links as you make them! Internal links, or links to pages within the same website also get 404 errors from time to time. Unfortunately this is due to the webmasters neglect of his own website. If modifications were made to the website, he should have checked his website, or ran an automated program to check all of his links. Broken internal links look bad and unprofessional. There are a few ways that a webmaster can mask his errors, or at least do some recovery work if an error occurs. If a webmaster changes the framework of his website he can create re-direct pages that will move the user to their the main index, or the updated version of the page that they requested. Additionally, they should be able to stop 404 Errors all together by creating an automatic forward whenever an error occurs. A couple tricks for webmasters to help reduce the amount of 404 errors, or try to hide the errors is to modify the .htaccess file in their website directory. This file has one variable that can be set that will allow you to specify the page that you want to send the user, should a 404 occur. Example: ErrorDocument 404 index.php The first example would automatically send the user back to the main index (if the main index was called index.php), and the second would send them to a customized 404.php file, which could display an error message, or send you an auto-notification of an error that happened. Keep in mind that if you use non-absolute directories that you may not feed out the correct page. For instance if the error occurs in a subdirectory on your website, and you specify index.php as your error document, there may not be an index.php in that subfolder, thus it might be a good idea to put the below example instead. Example: ErrorDocument 404 http://www.yoursite.com/ Note: If you use Apache HTTPD you can setup the default error documents in the configuration file! ErrorDoctor: 5,000,000+ Users Worldwide! - Add ErrorDoctor to your Review Site and watch the sales come in! Scan And Fix Errors In Windows Registry. - Error Nuker - Scan your Pc for Free to Check for Windows Registry Errors - by SpyWare Nuker Team - no#1 money maker since 2002. This post comes a bit late in the whole web 2.0 cycle. I feel that it bears repeating because I have come across sites that don't follow some basic principles when pulling in 3rd party data from sites such as flickr, twitter et. al. APIs and data portabilityThe blessing of popular and easy to use APIs and the data portability of web 2.0 applications has had an unfortunate side effect, and that is that some implementations that use these services do not integrate appropriate contingency design should these 3rd party services fail. Caching data calls to APIs is a good bit of contingency design. Many APIs will require caching - like that of Amazon - but I suspect this is intended to help limit resource use of the API host, not the site using the API. The reasons a person using API accessed data on their website would want to cache the data are:
A simple implementation to handle those two cases would be one that caches an API call for a given amount of time and one that freshens stale cached data and triggers an error should an API call fail. Caching is good contingency design practiceAs I said above, this post is a bit late to the party but it is worth writing as recently I have come upon at least three sites where firebug and other widgets have revealed issues retrieving API fetched data and the site loading times have been horrible. A decent implementation idea would be to roll your own caching wrapper and agnostically plug it in to a stable caching tool, perhaps something like Cache Lite for PHP. In this manner you have a reusable, caching library independent piece of code that can handle caching/flushing and refreshing of data which could function to handle the two cases discussed above. And that's it. It's been 541 days since my last post. Wow. I hope this is a re-start of a new phase of blogging. Article Index: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 |
More Articles:1. User Friendly Website Hints and Tips A very wise person once said something along the lines of “the best thing about the web is that every one can become a publisher and the worst thing about the web is that everyone can become a publisher.” With the availability of so many web publishing tools, developers are making it incredibily easy to design webpages and sites that are just wrong on so many levels.The golden rule applies to the web too! If it frustrated you on someone else’s website - why are you going to put it on yours? Belo… 2. Web Site Templates and Thier Benefits Unarguably, the most important part of your website is content. To draw in clients or customers, you need captivating content and search engines are blind to web design. They only see content. The images, structure and colors of your website go out the window when it comes to search engine placement, which we all know is the single best traffic generator. Your web design is really only a shell that makes your content look pretty. Don't get me wrong, your site's design can be very important. Peo… 3. Top Ten Ways to Increase Web Sales - Part 1 By Judy Cullins You have only 10 seconds to impress your potential buyer. Your Web site visitors don't care about you. They care what you can do for them. Give them a reason to buy. If you haven't reaped the sales you deserve apply these ten tips: 1. Write dazzling home-page copy that gives your potential customers a reason to click to your product or service sales letter. Use hyper-linked benefit driven headlines that lead visitors straight through to a sales letter that includes bulleted benefits of your… 4. How To Double Or Triple Your Page Views? It's easy, just design and engineer your main page in such a fashion that people will click beyond it into the rest of your site. If you are like a lot of webmasters, you're losing a significant number of visitors as soon as they get to your front door. The 'main page' on any site is the doorway to the rest of the content of that particular site. But, the BIG question is....will the door open? Will the visitor turn the knob and push through the main page to see what's really in there? We faced t… |
||||