Update: It turned out to be a problem with the Lightbox plugin I was using. I’ve replaced it with another plugin that provides similar functionality, and the error has now gone away. Lesson learnt: having many scripts on the same page can be a recipe for disaster. Thanks Nuffnang for helping me work through this issue.
I recently added a Nuffnang ad to the sidebar — I hope none of you mind too much!
Anyway, all was going well until Internet Explorer threw a spanner into the works (well, well, which browser always throws a spanner into the works?).
It appears that on Internet Explorer 7 and earlier (using my particular WordPress template at least), the addition of the Nuffnang ad code can cause the page to fail to load with an Operation aborted error:
This error is particularly troublesome: after the hopelessly uninformative dialog box is dismissed, the page disappears and gets replaced by a navigation error page. (Thankfully, this hideous behaviour was changed in IE8, which might explain why I didn’t pick it up earlier as that is my installed version. But it still begs the question, why do people insist on using Internet Explorer?)
I’ve let Nuffnang know about the potential problem, and with any luck, it will be resolved soon.
In the meantime, I’ve made some changes to the ad code:
What this does is that it first checks whether the browser is Internet Explorer. If it is not, the Nuffnang script can be called upon directly. If it is Internet Explorer, an
/nuffnang.html is added to the document.
/nuffnang.html just contains a copy of the ad code as provided by Nuffnang placed into an otherwise blank HTML page.
Why? Isolating the Nuffnang ad code in a blank page by itself seems to avoid the error conditions as described by KB927917. But even if an error were to develop, the error would be confined to the
iframe and the rest of the page can still be displayed.
If you’re having similar difficulties, give the above a go and see whether it works for you.