Bob Crabb

spray

trace

seen

glacier

keel

bucket

erase

Webgyrl, I'm glad that worked. I think that we all sometimes need another person to look at a problem; I can stare at a file for hours and not see the obvious. One tool that I like to use for checking to make sure that tags are closed where I think they should be closed is Notepad++. You can click on a + or - in the left column next to the opening tag of an element to collapse all the code within the element. That's how I found this problem. The Web Developer tool bar for Firefox is also a great development tool. In answer to your question about the P tag not validating, the problem is that it is an upper case P. In XHTML, only lower case is allowed. You have several tags that contain upper case. Also, the head tag is missing from your template. This probably occured when pasting the doc type into the file (I've done that before too). I looked at this page, though, and it won't take much to make it validate. Essentially, add a head tag after the html tag, change all the uppercase to lower case, add an ending / to your meta tags, make sure that any "&" are escaped as "&" , and I think there is a script that doesn't have a type parameter. There might be a couple of other things, but I think that was most of it. Cheers, --Bob

Webgyrl, If you add the /div that I suggested above, you will also need to delete the last /div tag before the /body tag. -------------

Webgyrl, I think that I found the problem. There is a missing /div tag, so your header div isn't closed at the right location. Add a /div tag before the div id="bg" Then comment out the height declaration in the #wrapper definitions in CSS. I think that will work.

I hate it when that happens. I copied your code and tested it in my development space. Looking at the wrapper div with Firefox web developer, it shrinks to a height of 78px. That happened to me recently on a page where I had an inner container with some floating divs. I never did figure it out, but found that I really didn't need the inner container so I didn't pursue it. I'll continue to work with this to see if I can figure it out, but hopefully someone will come along who knows this problem, and knows more than me will step in with a solution.

The wrapper element has a fixed height of 1000px. >/*** Layout ****/ #wrapper { background: #ffffff; margin: 0 auto; width: 776px; height: 1000px; border-left: 1px solid #f0e9eb; border-right: 1px solid #f0e9eb; } Try commenting out the height: >/*** Layout ****/ #wrapper { background: #ffffff; margin: 0 auto; width: 776px; /*height: 1000px;*/ border-left: 1px solid #f0e9eb; border-right: 1px solid #f0e9eb; }

beard

An alternative to experimenting in your account, you might also consider having him install WAMP Server on his PC. http://www.wampserver.com/en/ This way, if any learning experiments that go awry it won't create problems in your account.

thank

This little "traveler iq" quiz on Trip Advisor is kindof fun. I haven't made it past level 10 yet, but will keep trying. http://www.tripadvisor.com/TIQGame?nl=Mu&pid=646

react

Although some scripts require certain folders to have permissions set to 777 (for picture uploads, etc), this has always made me feel uneasy. I suppose that part of that uneasiness comes from an experience about a year and a half ago of finding some unwanted "gifts" deposited on my site, an incident that fortunately I caught before any damage was done. Anyway, I read on another forum that a good way to secure writeable folders would be to disable php in that folder by including the following code in the .htaccess file for the folder: >php_flag engine off <Files ~ "\.(php*|s?p?html|cgi|pl)$"> deny from all </Files> That seems to make sense, but I wanted to ask for opinions on the advisability of doing this.

throw

kyle

track

trait

I'm glad to have helped. Don't feel bad about overlooking the solution -- I just spent half an hour trying to "fix" a program that was working correctly.

sale

empire