Thanks for the reply - No I don't I'm afraid.
I'm assuming as this occurred between 4.1.1 and 4.1.4 upgrade (and no extra mods have been installed) that it must be something to do with the vb code changing. I appreciate that a mod could still conflinct but ultimately it must be down to a change in one way the vBulletin code works. The fact that it happens so much in Firefox compared to other browsers and doesn't happen at all in Safari, and it only seems to happen to threads that have been viewed before, seems to indicate it's to do with the caching.
I'm assuming as this occurred between 4.1.1 and 4.1.4 upgrade (and no extra mods have been installed) that it must be something to do with the vb code changing. I appreciate that a mod could still conflinct but ultimately it must be down to a change in one way the vBulletin code works. The fact that it happens so much in Firefox compared to other browsers and doesn't happen at all in Safari, and it only seems to happen to threads that have been viewed before, seems to indicate it's to do with the caching.
Comment