Sticky If you are having problems with Kunena, please read this first

*** Topics merged ***

one month later..... up ?

Try to enable Joomla 'System - Mootools Upgrade' plugin

You cannot "enable" the System - Mootools Upgrade plugin in J! 2.5.1 because there is no such thing in J! 2.5.x.

Nonetheless, the problem is the same as the issues referred to in msg #1 of this topic. There is a Javascript library conflict caused by something loaded by another Joomla extension on the problem site (but I don't know white one it is). I would discuss your issue with the people who developed the jv-framework template; ask them if their template works with K 1.7.2.

I tried to disable all modules/plugins the problem is still there. I tried to reinstall joomla and kunena without jv-framework, using the main template, same problem.

fk97440 wrote: I tried to disable all modules/plugins the problem is still there. I tried to reinstall joomla and kunena without jv-framework, using the main template, same problem.

I should probably write an article called "When all else fails, try this":

This is what I would write in my article:

(1) Create a completely new "vanilla-flavoured" Joomla test site (it doesn't matter if you use J! 1.5.26 or J! 2.5.4 for this test). On this test site, do not install anything else. Do not install any other templates, or extensions like sh404SEF or Community Builder for example.

(2) Using this test site, install K 1.7.2. Do not change any of the original configuration.

(3) With this very simple test site, I would like you to try the same test. Do you have your original problem on this test site? If everything works then you have found the answer to all of your problems. You now have a working website! :woohoo:

(4) One by one, change your test site by adding the other extensions you have on your problem site. After adding each extension, continue to test Kunena to make sure that you do not have any problems. Either you will find something that you've added which caused the problem (and then you can fix it up or remove it from your live site) or you won't. If you don't find the problem on your test site then (again) you now have a site that works! And then you can use this working site instead of the one that you've got problems with.

The first three steps should take you less than one hour.