Question Kunena 1.6 will conflict with other components because of his mootools upgrade plugin

Actually there are also some Joomla specific bugs that needs to be fixed, too. And that's why it's good to actually use/test the latest version, as it allows us to fix bugs before J1.5.19 goes out.

In one week, Joomla will be shipping with Mootools 1.2 so developers will need to update their extensions

I can't believe they are doing this again. After the 1.5.16/17 issues, you would think they understood they have to keep this for 1.6 only
Not the place for a rant, sorry about that!

At the very least, I'd suggest that you do not impose this to your users. What I mean is that IF Kunena comes to REQUIRE mootools 1.2, you should have your own copy, rather than rely on Joomla 1.5.19 plugin, as otherwise it will prevent users to disable that plugin should it conflicts with pre-existing extensions on their site.

Cheers

Yannick

Actually we are doing our best that all the issues get fixed in Mootools plugin before J1.5.19 goes out. If we can test the plugin in real sites with real audience, it's more likely that most issues will be fixed and people are happy with J1.5.19. Most of the compatibility issues in Joomla itself have already been fixed.

Let's hope for the best then

Hi

The best happened I just tested J! 1.5.19 with the mootools 1.2 plugin on, and it works fine, so I assume if you upgrade your own copy of the plugin to that in J! 1.5.19, everything should be ok then

Rgds

No need for our plugin copy anymore. We worked hard with the Joomla team to test it and get it into Joomla core with 1.5.19

This is a great step for all of Joomla. We hope that many component and template authors upgrade their code and leverage the core MT plugin. It will lead to much cleaner loading sites that don't double and triple load is libraries for every installed component.