Tuesday, September 13, 2005

Van Driving 101

Today was spent from 8-5 in the lovely and beautiful Sterrett Hall. Oh so much fun, words cannot describe. It was difficult to stay awake through the presentations about driving 15 passenger vans. Not only because I had heard all the horror stories and rules/regulations before but also because it was really, really, really, really ridiculously hot and stuffy in the hall. Again. It's all about being flexible though. The only really frustrating part of the day was during lunch. Some of my fellow team members and myself were discussing a hot topic and really bonding through our discussion. A team leader came by to inform us that there was going to be an "activity" on the other side of the building and basically made us join the rest of the group. What was this important activity, you may be asking yourself. Well, I'll tell you. A huge game of tag. Now tell me, what was more important in the situation? An intriguing discussion that was developing bonds among team members OR playing tag with 180 people in grass that hadn't been cut in months? If you say the later, please do not respond. :)
At this juncture I would like to take a moment to say how blessed I feel to have a team of people who doesn't willing want to participate in "summer camp" as we fondly refer to things like what happened at lunch. We are, for the most part, fairly enthusiastic and willing to do our part, but we don't have to express ourselves with ridiculous chants, clapping or playing elementary school games. On a side note, I usually don't mind running around like a 5 year old, but there are always times when it seems to be untimely--this was one of those times.
completely changing subjects: P.T. starts bright and early tomorrow morning at 5:30 am. I'm hoping that some of the wind that is being generated by Hurricane/Tropical Storm Ophelia dies down by that time. I went for a run last night with a teammate and it felt like I was running the wrong way in a wind tunnel. It was pretty bad. Only time will tell. I do know that they are preparing us for a 5K at the end of training. Good times will be had by all.
Not much else to report besides the FACT that I am beginning to miss people from home. The initial enthusiasm of being in a new place has begun to wane and I am starting to feel a little lonesome. Generally this only happens in the evening when I don't have much going on. So, if you get a call and I just want to hear a familiar voice, please just humor me. Thank you, in advance.
Grace and Peace.


jon said...

After we paid for our kids summer football camp we found it tough to recover! I totally agree with you!

Clickbank Mall said...

Nice blog. Have you seen your google rating? BlogFlux It's Free and you can add a Little Script to your site that will tell everyone your ranking. I think yours was a 3. I guess you'll have to check it out.

Tip Of The Day
Increase Your Traffic by Recovering Your Lost Visitors

If you spend any time surfing the Internet, you've probably encountered a few error messages.

Error messages have numerous causes, such as misspellings, outdated links or internal server errors. When an error is encountered, your server will display specific generic error pages according to the error. These error pages are not only dead ends, but they are also very frustrating for your potential visitors

When your visitors mistype your web address or click on an outdated link and receive the dreaded error page, they'll most-likely click on their back button and never return. However, you can recover a majority of your lost visitors simply by taking the time to create some customized, user friendly error pages.

As servers run different types of software and do not function in the same manner, there isn't a simple method for creating custom error pages that will work with every system. However, if you have your own domain and your site is hosted on a Unix/Linux server running Apache, this article will assist you in creating custom error pages.

If you're not sure what type of server you're on, visit the following web address to find out: http://uptime.netcraft.com/up/graph/

Before we begin, keep in mind, editing your server files is serious business. Even one small typographical error can wreak havoc -- make sure you make a backup copy of any file you're planning to edit.

Guidelines for creating your error pages:

1. Create your error pages in standard HTML -- just as you would create any other web page for your site.

2. Don't alarm your visitors. Never include the word "ERROR" in large, bold text. Your visitors may immediately become alarmed and think they've done something to cause the error. Instead, be apologetic and encourage your visitors to click on the navigational links to locate additional resources and information.

3. Your error pages should look just like the rest of your web pages. Each error page should contain good navigational links, a search feature, and provide information in regard to the specific error they received.

If you'd like to see an example error page, visit the following web address:

Once you've created an error page, save it as the error name. For example, if you're creating a customized error page for a 400 Bad Request error, your page should be saved as 400.html.

Here are some of the more common errors:

400 Bad Request
401 Authorization Required
403 Forbidden
404 File Not Found
405 Method Not Allowed
500 Internal Server Error
501 Method Not Implemented
502 Bad Gateway
503 Service Temporarily Unavailable

Once you've created your pages, you'll need to access your server via FTP and create a new folder called "errordocs" where you store your HTML files. Upload your new error documents into your new folder.

Your next step will be to locate your .htaccess file and download it to your computer. (If you use FrontPage to publish your web pages, you cannot customize the .htaccess file, as FrontPage uses the .htaccess file. Editing the file may cause errors in your configuration.) The .htaccess file should be located on your server where you store your HTML files.

If the .htaccess file isn't visible, you can create one within a plain text editor. However, you must first make sure your server isn't configured to hide the file. Your FTP program should enable you to choose to display hidden files and folders on your server.

Once you've downloaded your .htaccess file, open it within a plain text editor, such as Note Pad, and add the following lines below any other text that may be present:

ErrorDocument 400 /errordocs/400.html
ErrorDocument 401 /errordocs/401.html
ErrorDocument 403 /errordocs/403.html
ErrorDocument 404 /errordocs/404.html
ErrorDocument 405 /errordocs/405.html
ErrorDocument 500 /errordocs/500.html
ErrorDocument 501 /errordocs/501.html
ErrorDocument 502 /errordocs/502.html
ErrorDocument 503 /errordocs/503.html

If you're creating your own .htaccess file, open a plain text editor and add the above lines.

When typing in the information, make certain you type it exactly as it appears above. You can include the error documents of your choice.

Once the file is complete, save it as .htaccess and upload it to your server, via FTP in ASCII mode, where you store your HTML files.

For additional information on File Transfer Protocol (FTP) you may visit:

If you have a Windows operating system, you will be unable to save the file as .htaccess. You'll need to save it as htaccess.txt. Once you upload the file to your server, you can rename it to .htaccess.

That's all there is to it. When your visitors click on an outdated link, your custom error page will now be displayed.

Creating your own custom error pages is well worth the time and effort, as they will enable you to recover an unlimited number of your visitors. If you follow this step by step guide, you can have your pages up and running in no time.

Website Design