Question Best way to resolve mootools conflicts?

Hi,

Just installed Kunena 1.6 and I love it! Great work, Kunena Team!

I'm hoping I can keep it installed on the site I'm currently working on. That will depend somewhat on whether I can resolve some mootools conflicts.

The upgraded mootools (1.2.4) is necessary for the forums, but it breaks so many other things on my site. I'm thinking about modifying the behavior.php file of the mootools 1.2.4 system plugin to begin with a conditional php check to determine if the url of the current page includes "com_kunena" - and only load the plugin if the case is true.

I'm not a programmer, however. Can anyone here give me some pointers on how to write such a check statement? (Or - if this is a bad idea, please explain why.)

Thanks!!

Any help that the community can lend to the project is appreciated. We don't believe that there is any need to tamper with the Joomla Mootools 1.2.4 Javascript library. Rather it is for the other incompatible plugins/modules/templates that need to be modified.

As we go forward, Kunena will use the standard tools and libraries available to all Joomla users. This is particularly important when Joomla 1.6 becomes available. The objective here is to ensure that Kunena will be compatible with Joomla 1.6 and those things available in that version. At the same time, it is also important to make sure that Kunena remains a viable option for users of J! 1.5.x, too.

I can appreciate your line of thinking. This, however, is the situation I'm facing today:

sozzled wrote: At the same time, it is also important to make sure that Kunena remains a viable option for users of J! 1.5.x, too.

I was hoping to find a viable solution that would allow me to launch a site using K-1.6 next week. Realistically, all the other components I'm using cannot (will not) be rewritten to use mootools 1.2.4 in that timeframe.

I'm open to suggestions for an immediate fix, with the understanding the fix will be temporary until other components are brought into compliance.

Here is my totally honest recommendation to you, and to others who may be in this same situation.

If it is absolutely essential to keep old, legacy software that will not transfer to Joomla 1.6 (notice, I did not say Kunena 1.6) then maybe you should stay with K 1.5. As long as you are aware that there will come the day when J! 1.5 will no longer be supported and as long as you're aware that K 1.5 will not be developed any further - and that none of the advances made in K 1.6 will be backported to K 1.5 - then you have to accept that you're painting yourself into a corner.

It's a question of personal choice. If the other components on your website are more important than having a reliable, robust, durable, error-free forum then you shouldn't worry about the forum. That's your choice and we totally respect that. If, on the other hand, you want to future-proof your investment with leading-edge technology then you need to get rid of the old technology.

In your case, you're likely to have few implementation issues with K 1.5 but you will probably have more problems down the track.