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

sozzled wrote: Have you tested Joomla 1.5.22 + K 1.6.2 on a test site (on your server) with no other extensions, using rhuk_milkyway template, just to make sure that this problem is not a Kunena problem?

Have you done this first: J 1.5.22 + K 1.6.2 + rhuk_milkyway + nothing else? If that don't work, let us know (and save yourself the costs of hiring a developer).

sozzled presumably you mean to do this on my live site? If so will the ruk_milkyway template work given that the site is configured to work with js_fresh?

Thanks again

No, "presumably" is not what I intended.

I mean do this: on your hosted domain, create a subdirectory/subfolder, whatever you want to call it, and create a new, discrete MySQL database, and install Joomla 1.5.22 into that. In other words, create a test site on your hosted webspace, on the same server that runs your live site. Do you understand what I mean?

When you have created this new test site, install K 1.6.2 on it. Then tell us if you have these "Mootools" issues. I will bet you that you don't! I think you are chasing the elusive White Rabbit going after js_fresh, but that's just my opinion.

I can already tell you for sure that it will work as it used to work when I used a different template 6 months ago. And now you are going to say that you are certain the problem stems from js_fresh but the way to see if that is valid is to set up the subdomain with js_fresh,latest joomla and latest kunena am I right?

Pereira wrote: After an update of joomla PT from 1.5.15 to 1.5.22 and an Upgrade from Fireboard to Kunena 1.6.2. Everything is ok, except the user profile editor. I have been reading all the 4 threats in the forum around this problem. I am going to post my situation (sorry if I shouldn´t post my web site).

My profile user page is: www.matospereira.com/np/forum/perfil.html

user:test
password:test123

Are you able to help me? thanks!
Where should I start?

daviddmf wrote: And now you are going to say that you are certain the problem stems from js_fresh but the way to see if that is valid is to set up the subdomain with js_fresh,latest joomla and latest kunena am I right?

No, I'm fairly certain that the problem is a Javascript library conflict with Mootools 1.2.4 on your website and fairly certain that the problem is not a Kunena issue per se. I have a strong hunch that your site template (or something added by the template, more precisely) is at the centre of these problems.

If you eliminate Kunena as the cause of these problems then what's left? That's what you have to focus your attention on.

The thrust of Which came first, the template or the forum? is to focus attention on the purpose of people's websites and the planning that goes into building them. If people are primarily concerned with the way the site looks (and not how it behaves) then this topic - [Merged topic]The great Mootools/Javascript conflict discussion - is a not where people need to look for help.

Our objective at www.kunena.org is to help people enable Kunena on their websites. We can only offer advice. We cannot decide for others how they conduct their business. In the final analysis, the choice may come down to whether Kunena is viable as the web-based discussion forum component for their internet business. We understand and we respect those choices that people make.

But, before this discussion turns into a "is Joomla the right choice for my internet business" debate, let's stay on-track. You have a problem, we believe that we've isolated the cause, and the solution really lies in your hands.

Pereira wrote: Where should I start?

You have 9 Javascript libraries running on your Kunena page; K 1.6 uses 3 Javascript libraries. One (or more) of the other 6 Javascript libraries is clobbering Mootools 1.2.4. You should start by reading through this discussion topic, try some of the suggestions that others have tried, read the background information and make sure that you do have a reliable test site to do these things.

In the final analysis, if you cannot solve this problem yourself then you may need to engage the services of a website software specialist.

In my case I suppose it´s a module conflict with mootools, because I have tested changing to BEEZ and JA_purite themes. The problem in profile stills there, I am using legacy mode. I am hable to use legacy mode with kunena or is it really an impossible situation?

Do not use "legacy mode" - that's very important!

Not all of these Mootools/Javascript library conflicts are caused by the site template; they can be caused by any Joomla extension that you use. You need to look at all the Joomla extensions that you have on your website. Focus on Joomla extensions that were written a long time ago (more than 12 months ago).

This is not an "impossible" situation. The success rate is about 85% - those who do not resolve this problem give up, go back to K 1.5.13 or they try another product. FYI, both of the two main forum components that integrate with Joomla (Kunena and Agora) use Mootools 1.2.4, so this isn't really a problem that's going to disappear simply because people think that they cannot use Kunena. There are other forum components that you can use but they either (a) do not integrate directly with Joomla or (b) do not have an extensive range of features.

It´s a battle to me. Legacy Mode OFF.... I removed all modules that requested legacy mode...even docman. No success till now.