Question [Merged topic]The great Mootools/Javascript conflict discussion

I'm having an issue with yooPhoenix and Kunena and CB.

When I turn on integration with Community Builder in Kunena something happens to the style and in IE I see a small white box appear at the bottom of every Kunena page, it doesn't appear in FF.

I dont' see how to turn off Mootools in the yoo template, can you tell me how?

Maybe it will help...?

Kohhal wrote: I'm having an issue with yooPhoenix and Kunena and CB.

When I turn on integration with Community Builder in Kunena something happens to the style and in IE I see a small white box appear at the bottom of every Kunena page, it doesn't appear in FF.

I dont' see how to turn off Mootools in the yoo template, can you tell me how?

Maybe it will help...?

Please make a new topic. This one is fixed.
1) but for your first question, please read this topic:http://www.kunena.org/forum/171-k-16-templates-and-design-archive/83088-ie8-problems.
2) Must be a setting on the template settings.

regards 810

G'day, itcc, and welcome to Kunena.

As you can see by browsing through this topic, a lot of other people have reported the same problem - i.e. they see tabs but no information below them in Kunena user profiles - and they are unable to edit their user profiles because of this problem.

The problem is caused by a conflict between some Javascript library that is loaded by one of the Joomla extensions they are using and the standard Joomla Javascript library Mootools 1.2.4 . The difficult part is finding out which extension people are using that is causing this problem. The problem is made more more difficult when you have a lot of Javascript libraries loaded.

Kunena 1.6 requires 3 Javascript libraries:

• ../plugins/system/mtupgrade/mootools.js
• ../components/com_kunena/js/mediaboxadvanced/js/mediaboxAdv.js
• ..//components/com_kunena/template/default/js/default.js

In your case you have 5.

One of the classic symptoms of the Mootools Javascript conflict is increased page load times. Look at the bottom of this page and you will see a time of about 0.50 or thereabouts. In your case your page took 11.5 seconds to load! That's a huge amount of time.

So what is the specific cause of your problem? I don't know but I'm guessing that it's the cssmenu.js that is loaded by your site template. Try using a different site template for your Kunena forum pages (like rhuk_milkyway for example) and see if it makes a difference. jxtc templates are a known source of Mootools conflict problems. If you continue to have these kinds of issues you really should be asking them why their templates are not compatible with Joomla 1.5.22. I hope this helps.

Thank you very much for your reply.
I solved my problem by editing index.php file of my jxtc template (I turned off two JS libraries), and now I'm able to edit and save my profile, and also the bb code issue is solved.
Kunena's front page is still slow, but I hope I'll manage that issue with template update.

Thanks again!

Sozzled pointed me to this topic (thanks)

Some people have gotten around the whole mootools problem by enabling mootools only in Kunena's pages by either modifying Kunena's initialize.php or by using loadplugin_CK module (I've had no such luck so far)

So if anybody else has solved their issues in those ways, please explain how, I'd really appreciate it



I forgot to mention, I have some components that I really need and can't replace, and I have to disable mootools for them to work properly.

daviper wrote: I forgot to mention, I have some components that I really need and can't replace, and I have to disable mootools for them to work properly.

If that is the case then, maybe, you will never be able to make K 1.6 (or any future version of Kunena) work for you. Sorry.

daviper wrote: So if anybody else has solved their issues in those ways, please explain how, I'd really appreciate it

This discussion topic is full of success stories. Over 95% of the people who have written to this forum (and whose messages have been merged into this discussion topic) have solved their problems.

Most of these problems can be solved yourself. For those who cannot solve those problems (or who do not have the time to wait) there are professional services available that you can employ to work with you to resolve these issues. However, as I mentioned earlier, if there really are components that are causing the problem - and you cannot do without them - then that's your choice and we accept those conditions.

And that's exactly why I posted in the other thread. Because those people had exactly the same problems as me and it appears that they've solved them.

As far as I've been able to find out, if BBcode in Kunena doesn't work just because mootools is disabled, and that's your only problem with Kunena, you can solve it pretty effectively by enabling mootools in Kunena's pages and you can still leave the plugin itself disabled.

daviper wrote: And that's exactly why I posted in the other thread.

"Other thread"? Could you please clarify what you mean by this?

daviper wrote: As far as I've been able to find out, if BBcode in Kunena doesn't work just because mootools is disabled, and that's your only problem with Kunena, you can solve it pretty effectively by enabling mootools in Kunena's pages and you can still leave the plugin itself disabled.

This has been a tough discussion to moderate. For some people they have found that the answer is to enable the System - Mtupgrade plugin. As far as I can tell, this should have no effect at all on the issues. Kunena enables the plugin anyway (even if you've explicitly disabled it).

For other people they've discovered a solution by disabling the System - Mtupgrade plugin; this may have nore success as far as preventing contention with other components installed on the site but, again, it should make no difference as far as Kunena is concerned because, as I wrote above, Kunena enables this plugin anyway.

The solution, as we have repeatedly tried to explain as clearly as we can, is not simply a matter of enabling or disabling the System - Mtupgrade plugin. The solution is to determine what other extension is loading a Javascript library and to make sure that the way that these libraries are loaded occurs without them conflicting with Mootools 1.2.4. The difficulty is in determining what are these extensions that people have installed that cause these conflicts. Each person's situation is unique.

The problem does not lie with Kunena. The problem lies with the developers of Joomla extensions who have implemented their own Javascript methods/functions/behaviours that conflict with the new standard for Joomla.

One way you can achieve this is to remove other extensions from the Kunena pages. You can, for example, use a different Joomla template (one that is Mootools 1.2-compliant). But, as I've said on numerous occasions, every case seems to be different.

I meant this thread: demo16.kunena.com/forum/114-user-written...r-kunena-pages#87331


First of all, I don't envy you, because I've seen how many replies you've added to this discussion and I think Kunena has some of the best forums in general, when it comes to joomla development.

Yeah, I know the problem doesn't lie with Kunena. Unfortunately some developers don't seem to care enough about mootools enough in my opinion. I came across so many components in the past year that have mootools issues, that I've stopped counting them honestly.

I know it would probably be easier to remove the components that are having mootools problems, but I just can't. I've bought a pretty expensive component, and I've just recently discovered that it doesn't work with mootools enabled. And my website is finished. Everything is done, and I've done a lot of work to modify Kunena, that's why I'm willing to spend so much time and effort on getting it working properly.

So I can't change the components, and Kunena is one of the vital parts of the website.

Even with the correct URL ( www.kunena.org/forum/114-user-written-ha...r-kunena-pages#87331 ) the point is that Mootools 1.2.4 is a required piece of software for K 1.6. See K 1.6 Technical Requirements . However, I thank you for pointing me to the "other thread" that you were referring to.

I have, in my working life, encountered many cases of the "protect the investment at all costs" approach that many IT managers use when they justify the strategic directions taken by various organisations and businesses. It's always difficult, when you pay a lot of money and realise afterwards that the solution doesn't work, to take the tough decision that maybe it's not worth throwing good money after bad. Nonetheless, you've made done what you've done and no-one is going to say that your choice was the wrong one. But there are always options and that's what I try to keep as my main focus.

One of those options is to engage a professional - a specialist - to work with you (for a fee, of course) to see what can be done to salvage a workable solution with the software that you have chosen. If this approach appeals to you, please let me know by PM and I'll see what I might be able to offer. There aren't any guarantees, of course.