The problem sems now to be mainly in the Community forums and in the New Posts function.

After much discussion and gathering and emailing of evidence I have left it with T-mobile. Although very helpful the guy on the helpline had to admit that he couldn't see what the problem is and needed to pass it on to their software engineers. He promised to get back to me with a progress report by the end of this week.

And I have no idea what your reply to "No real progress", Kalleh, was as I can't see very much in this forum.

Still, at least I'm posting in the other forums to the extent that I can.

The current state of play seems to be that the engineers have replicated the problem using IE (though interestingly not Firefox) and have identified that it seems to be related to javascript optimisation and reported it back to the same third party supplier that the bug affecting the chatroom was reported to.

I'm expecting a call from the support team this afternoon and I'll keep you updated.

(As ever this is in a forum I probably won't be able to see at home - I'm sending this from work.)

It appears I have a workaround.

The problem has been, as I said, reported to the third party software company but, at the T-mobile suggestion I have retried using ctrl-F5 when I get the fault and it does seem to work (on this computer anyway, haven't tried the laptop yet.) Maybe a touch inconvenient but certainly workable.

Would that make chatting possible?

Doesn't seem to, but hey, if it gets the main site back that has to be a plus.

This message has been edited. Last edited by: BobHale,

Boy it feels good to have a workaround that's given me access to the whole site again. It's been like having an arm cut off.