12-06-2011, 11:11
An issue was raised in the "Slow Board & "MyBB SQL Errors" thread of double posting in the forum. The issue was raised in that thread because it was being linked to the general performance of the site. This was incorrect as it's actually an issue with Internet Explorer. The 4 members who have reported this issue - vila, mr mystery, whizzer and rickhardo - are all using that browser (probably IE9, although vila said IE8).
It was stated in the "Slow Board & "MyBB SQL Errors" thread by vila that the problem only occurs on this site and is therefore specific to the forum. This is incorrect. Many other forums have experienced the same problem and not just forums running the same software that we do. The same problem has also been reported as occurring on facebook and twitter. Most explanations of this issue say that IE9 is the culprit, but vila said he had the problem with IE8 and I also know of a couple of other people who said that they have the problem with IE8.
It's suggested by some that the issue can be resolved by adding any sites where you have this problem to IE's compatibility mode. I have not tried this myself as I rarely use IE when visiting the forum, so I can't verify that this fix works here, but that's the only solution for this issue that I'm come across so far.
It was stated in the "Slow Board & "MyBB SQL Errors" thread by vila that the problem only occurs on this site and is therefore specific to the forum. This is incorrect. Many other forums have experienced the same problem and not just forums running the same software that we do. The same problem has also been reported as occurring on facebook and twitter. Most explanations of this issue say that IE9 is the culprit, but vila said he had the problem with IE8 and I also know of a couple of other people who said that they have the problem with IE8.
It's suggested by some that the issue can be resolved by adding any sites where you have this problem to IE's compatibility mode. I have not tried this myself as I rarely use IE when visiting the forum, so I can't verify that this fix works here, but that's the only solution for this issue that I'm come across so far.