BootsnAll Travel Community

Hi all,
I'm having a minor difficulty with my 'blog (really? I wouldn't have gathered that from the subject of the post)

Specifically there's a large blank area between the header and the top post. Perhaps 800 pixels deep. Can anyone explain why this is happening and how to fix it?

Many thanks.

From my computer, it looks just fine.

Donovan

From mine

Its fine in firefox and opera but ie has the huge white gap.

The gap is the same height as the content in the sidebar, so it looks like something in the stylesheet is affecting ie only or maybe a missing </div> in the theme ie's falling over on?

Would need access to the theme to help beyond that, sorry

I seem to have the same problem with mine. Originally I thought it was the movies I'd whacked up there being too wide, but it happens on all the entries. Even if you go to the stats page, it doesn't appear until you scroll down to the bottom of the menu bar on the right.

oh, and the title banner at the top is much thicker (or taller) than usual.

Well...

Looking at the source for both those sites what you'd class as the page content is coming after the sidebar.

I'd expect in the code to see

header
content
sidebar
footer

Both the blogs mentioned in here have

header
sidebar
content
footer

which explains why the contents coming below the sidebar. The code within the header is also back to front. I saved the source of beakers and rearranged it and the formattings spot on then..

How much control (if any) do you have over the templates with these blogs? I'm guessing not enough for this so it would be a fix for the bootsnall folks...

Yep, you're right about the level of control over the templates.

Thanks very much for taking a look for us anyway!

I'll have the blog templating trolls take a look at it.

The problem stems from images that are too wide for the template content area. Basically, if you're posting an image that is wider than 500px IE freaks out and the result is what you see. Firefox automatically re-sizes images to fit, which is nice. How to deal with this problem is covered in our Blog FAQ.