theiconoclast

Thank you so much! That program also sounds very useful ??

Great link. I know of the WC3 validator, but I always tried it on the Index.php page and received a message without much elaboration. Thank both of you so much for your help.

I have done that. Here’s how my pages are outlined:

#page
[header]
#container
[main-stuff]
/container
[footer]
/page

The <div id="page"> and header are in the header.php file. The footer and the </div> for #page are in the footer.php file. My template files just contain a <?php get_header(); ?>, the container/main-stuff, and then a <?php get_footer(); ?>.

The div for #content starts and ends in the template pages, so I don’t see how it can affect the footer.

Thanks for the replies, by the way. I really appreciate it. This whole thing has me stumped.

After multiple edits, I’ve deduced that the About page is working as it should. The parent, for the About Page, is #page.

In the other two, however, #content is the parent. Why would this happen? How would I go about fixing it?

All the pages have the <?php get_footer(); ?> at the end, so shouldn’t they be consistent?

{Last edit, promise!}

Triplecheck your CSS as well. I had the same problem and it was simply a missing “>” from the end of a </div> tag.

Well, I feel kind of silly. I can’t edit my post anymore, but for future reference, I forgot to do this:

“#footer
{
clear: both;
}

This tells the browser not to allow any floating elements on either side of the footer. When we look at the site now, we will find that the sidebar has been neatly tucked in the proper place, and our page matches the original design. Putting the footer hr inside the div ensures that the hard-rule doesn’t get wrapped as well.”

From UrbanGiraffe’s WordPress guide.