I don't have access to a WinXP system running an original version of IE8. Therefore, the only test I could run was on a Win7 system with IE9 simulating IE8 and, as far as that test went, I had no problems when I
hovered the mouse over the
Kunena menu. It is, however, clear to that you have a Javascript "software soup" whose ingredients are overpowering one another.
Let me put these issues into perspective. In msg #1 of
Before you post your question, read this first
we discuss various issues that cause the non-performance of
Kunena on people's websites. If one studies the "form guide" over the past few years, it's a safe bet that as one introduces another Javascript library into the mix, the probability that it will not co-operate with others increases until it becomes a certainty.
Joomla needs the following Javascript libraries in order to work
Code:
<script src="/media/system/js/mootools-core.js" type="text/javascript"></script>
<script src="/media/system/js/core.js" type="text/javascript"></script>
<script src="/media/system/js/mootools-more.js" type="text/javascript"></script>
Kunena adds two more
Code:
<script src="/media/kunena/js/mediaboxAdv-min.js" type="text/javascript"></script>
<script src="/media/kunena/js/default-min.js" type="text/javascript"></script>
That's the
minimum set needed to run
Kunena in J! 2.5. In a "vanilla-flavoured" J 2.5 website using the Beez5 template, the total number of Javascript libraries running (when
Kunena is loaded) is 7.
In your case, however, I counted a total of 24 Javascript libraries, any
one of which could be responsible for clobbering Mootools in an
Internet Explorer environment.
Although I did not encounter any problems (in the 10 minutes that I spent looking at your site) with
Firefox - I'm not saying that there aren't Javascript conflicts even for
Firefox, it's just that I didn't find any - I
did encounter the Javascript errors with IE9.
Several elements on your
Kunena pages, when clicked, produce the same "Invalid Argument ../media/system.js/mootools-core.js [at] line 354" errors.
What's the solution? Ultimately this is a decision that only you can make. I suggest you read
Which came first? The template or the forum?
and then look at the practical guide given in msg #1 of
Before you post your question, read this first
.
When you say "at one point your upgrade failed" I think we should be discussing those issues in a separate topic where we can give it the focus it requires, rather than diffusing the focus away from the principles on which Javascript operates in an
Internet Explorer galaxy "far far away".