ROCKETTHEME IS CLOSING ON JUNE 30, 2025. As a thank-you to our community, enjoy 50% off all themes with the promo code THANKYOU before we shut down.
Read our Farewell Blog Post for more details.
The dreaded Mootools causing operation aborted error in IE
Posted 16 years 5 months ago
I am trying to use the moseasymedia extenstion and also a snippet from weather.com. Both of these scripts are called out within the body tag. I am using terran tribune but it doesn't seem to matter which template I use.
I did some googling and came across some information about the dom or appending child nodes.
I am not exactuly sure how to fix this but it happens with any javascript added within body tag.
With either I will get the error once but if I go back to the page it will be fine, then if i reload a couple more times i get the error again, that what led me to believe it could be the domready problem. I also tried just loading the JWFLV player manually but had a problem with it stripping my script in the article even though I am not using a wysiwyg. Someone else was able to get the JWFLV player to work in an article but then gets the operation aborted error as well.
It actually doesn't appear to be a template specific error but I am trying to use terran tribune and if I use the fix at the end of this thread it stops crashing although my rokmininews does not work.
It seems to be a problem with the mootools in the behavior.php file. If I could get mootools to load at the end of the page I am guessing my problems would go away. Any help would be great.
I am unable to give a demo link, this is being tested on our companies internal servers.
This thread provided alot of information but I am unsure how to apply it or if it even applies.
Re: The dreaded Mootools causing operation aborted error in IE
Posted 16 years 5 months ago
I have it narrowed down, if I replace all of the domready's with load in my mootools.js file IE stops crashing but then the rocknews rotatator on Terran Tribune quits working.
Is there a way to only load mootools.js on the front page? Or better yet not load mootools.js on my podcast page?