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

I'm having the * EXACT * SAME * issue. I'm running the Rockettheme Panacea template.
You explained the problem EXACTLY as I'm experiencing.

If you find what the issue is could you please email me the info?


Appreciate it!

abqdavid wrote: I'm having the * EXACT * SAME * issue. I'm running the Rockettheme Panacea template.
You explained the problem EXACTLY as I'm experiencing.

If you find what the issue is could you please email me the info.

No need for us to email you with anything. Please contact Rockettheme with details of your problem and they will provide you with the solution.

I am not able to change any profile setting even as an Admin. Here is a screen shot

grab.by/6MTP


I tried to access this post, but I am not able to the page is just white.

www.kunena.com/forum/159-k-16-common-que...file-after-upgrading

Thank you. Yes, I've seen this problem before. Yes, we are aware that there is a problem with the message that you referred to; the team has not yet fixed that problem. We are sorry for the inconvenience.

My recollection of the problem that causes the profile edit tabs to "dangle" with nothing shown below them is due to a Javascript conflict issue. That is my recollection. Unfortunately, I wasn't able to locate where I had seen this issue before and how we resolved it. My memory - which is not always 100% reliable - suggests to me that the problem lay in the site template used in that case and, as I also seem to remember, an Artiseer-generated home-grown template came into play. I could be quite wrong on any or all of these scores. One thing is for certain: it's a Javascript conflict issue and that's where you need to start your diagnosis: see Mootools 1.2.4 and BBCode editor / Quick Reply not working (and other JavaScript issues) .

The answer to the problems(s) involves a process; the answer is not "click-this-and-it's-all-solved" neatly-packaged solution ... unfortunately.

Can anyone make a final conclusion the problem?

Yes we can: the final conclusion on the problem is that the problem is not caused by Kunena. We're trying to avoid a finger-pointing exercise here when many people are saying "it's all Kunena's fault". It's no-one's fault, really. The problem is caused by the fact that people have chosen certain Joomla extensions that have introduced their own Javascript libraries and those Javascript libraries clobber Joomla's standard Javascript libraries.

Kunena uses Joomla's standard Javascript libraries.

Kunena needs Javascript to work. If you eliminate Javascript you might as well eliminate Joomla (in fact, Joomla won't work without it, either).

The problem is caused because some Joomla extension developers were unhappy with Joomla's standard Javascript libraries and they developed their own. No problem there. Joomla is open-source, you can do what you want. So, developer A built his own library, developer B built hers, developer C did theirs and so on and so forth. (Once upon a time Kunena had its own modified Javascript libraries, too!) K 1.6.0 uses Joomla's standard Javascript libraries. If other software won't work with Joomla's standard Javascript library that's when some problems may arise; if other software clobbers Joomla's standard Javascript library then that where most of these problems occur.