Not sure what's going on, but the forum is floating in the middle of the width of my monitor - which is fine - but every time I click on a link anywhere in the forum the page stretches to fill the width, the link moves so I have to click it again.

Someone been messing with the code?

Broken it again

Blame it on Rob

Scott & Chris are back today so things should be sorted soon

this is happening to me at home on my desktop pc

it seems like in the code the forum is set to a certain resolution width, then when you click a link it refreshes to fit your resolution

Still happening, really annoying still!

https://www.youtube.com/watch?v=w40t03w1FIk

agreed. almost 4 weeks since it was reported (i know xmas and new year etc) but still not one word from an admin

not good

Apologies for not replying earlier. The problem wasn't (and isn't) happenning on any of my devices when I came home, so assumed it must have sorted itself out. Can't promise anything, but I'll see if I can find anything out.

Sorry guys but Xmas and my wedding too priority. If I had of seen a problem when using my phone/pad I would have got onto it but this is the first I've seen of the issue.

I shall have a look on my laptop at the weekend. I don't have a spare second to myself before then. I do apologise about the issue though. Unsure what's causing it at current but it's more than likely going to be incorrect HTML code causing the. CSS to bust out. Ill feed back with what i find. I'll need to replicate it first.

Can you let me know be browser being used and version please?

Windows 7 64-bit - latest version of Chrome.

same as Nick

Easy use Firefox instead lol

Use an iPad & Android phone, job done

I use chrome and i dont get it

firefox is crap, dont want to browse the forum on my ipad or android phone, im not that desperate that i need to check it on the go.

Only check it in the office on my work laptop or at home on my desktop

It's not about desperation, it's about convenience

Hopefully the issue is sorted asap

Problem also present on latest Chrome, Mac OS X 10.9.5.

Looks like fluid width CSS settings tbh!

Yeah, exactly what I thought

Bit harsh

how is that harsh

firefox IS crap
and
im not having a go at others for mobile use, i'm saying personally I don't feel the need to check the forum on the go. There is nothing I or anyone posts on any forum that is important enough for me to want to check on the go, I check when I get home or at work sat at my desk behind the PC

still happening all the time

Yep, same. Keep clicking on links wondering why it's not loading then realised I've only clicked to widen the page, then have to click again.

It never used to happen so it's a recent change to the CSS/HTML that has caused it...

Looking at it. Seems the banner has more spacing around it. I'll have a peek and look at the HTML. Doubt it would be the CSS. Very rarely change anything there.

Nick. Are you able to test this and throw a screenshot up for me? I've changed the HTML today but cannot test it out?

I don't have a Mac. Does this happen on any Windows browsers?

Cheers

You've now squashed the layout on the iPad and phone Scott......!!??

It seemed to work OK for a few hours yesterday, now it's back to doing what it was doing.

I haven't tried on my Mac, it's on my PC where it's more prevalent... Windows 8.1 x64, latest Chrome.

Web Inspector is telling me this:
ubb_jslib.js?v=7.5.8:59 Refused to set unsafe header "Content-length"
ubb_jslib.js?v=7.5.8:60 Refused to set unsafe header "Connection"
http://fordfiestast.co.uk/625.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
ubb_jslib.js?v=7.5.8:59 Refused to set unsafe header "Content-length"
ubb_jslib.js?v=7.5.8:60 Refused to set unsafe header "Connection"
ubb_jslib.js?v=7.5.8:59 Refused to set unsafe header "Content-length"
ubb_jslib.js?v=7.5.8:60 Refused to set unsafe header "Connection"
ubb_jslib.js?v=7.5.8:59 Refused to set unsafe header "Content-length"
ubb_jslib.js?v=7.5.8:60 Refused to set unsafe header "Connection"

Even better than screenshots (as they won't show you anything), a screen capture.

https://www.youtube.com/watch?v=-s454CSzBo8

Looking back at the video, the main index is a different width to the individual forums, there's just no consistency in the width - the gaps along the top of the forum between the header and the random image on the left are a bit strange. If the title is long enough and you click on the left of the topic title it will go straight in, if you hit the middle or the right of the topic title the forum width expands then you have to click again.

Very occasionally, some forums automatically fill the width when you load the subforum index but not before appearing as a thinner version.

My suggestions would either be - a properly implemented fluid width layout, or a properly implemented fixed width layout, at the moment it seems to be a mix of both which doesn't appear to be working properly.

EDIT: The banner isn't central to the forum layout and the random image on the right is aligned as far to the right as possible which is only in alignment with the main forum index, it's out of alignment and offset where-ever else you are in the forum.

My personal view would be to ditch the random photo element, create a new table row above the breadcrumbs and use that for the header rather than sticking the header into the body element.

Much better - scales properly when resizing window, automatically takes up 100% width. Cheers!

Nope, gone again!!

Still buggered on moblie devices.....

Yea it's far too small on iPhone now

The layout doesn't favour mobile devices - a mobile skin or Tapatalk would be perfect but that hasn't materialised

not sure why but today the page seems to be over lapping my screen

Suspect it's related to the issue reported earlier in the thread Kenny.

I assumed from the silence that it's something that can't / won't be fixed so I just stopped mentioning it

oh right well its the first time it has happened on the work computer

it was fine yesterday now this morning its doing it again

I'll look into this again. Seems we can't get it right for all the different browsers.