Mootools conflict between Sporter/Kunena

I upgraded to the latest stable ver of Kunena last night and lost the BBCode editor in the forum. After reading through the Kunena doc on the issue and testing Sporter and Kunena locally, it does look like there is an issue with the template js. The problem goes away when I switch back to the default Joomla template.

What sucks more is that on my live site , switching the template doesn't fix the issue. So, I guess there's an additional component conflicting besides the template.

This is all greek to me. If anyone can help with a suggestion I would be grateful.

Just to confirm that the template is conflicting with the BBCode editor in Kunena, I disabled a bunch of the modules and plugins on the live site. The problem was still present in the forum. I then switched from Sporter to the Joomla default template and everything is working within the forum.

- Can/will this issue be addressed?
- Approx timeline to getting a fix?

Sorry if I'm coming off as a PITA, but I was so thrilled to be using the template and now it's the reason my site is offline. Hope you can help resolve this.

For others using Mootools 1.2 on your site, I found this within the forum. Basically, what it comes down to is the Gavick templates do not support the latest MooTools. If you are running Kunena 1.6 or any other features that require Mootools 1.2, don't bother with these templates. For others thinking of using the template and extensions to reproduce the look of the sample site, you'll also have issues with a few of the extensions.

What bugs me most is that we pay for these templates. It would be nice if one of the developers could take a moment and point this out when people post or email the direct question. You don't win any fans by ignoring customers.

They have addressed the Mootools 1.2 issues many times, the search button is a wonderful tool

To bring you up to speed they're working on updating the templates to 1.2 as we speak, no real point in updating the templates to 1.2 if the modules don't work with 1.2. So if I was them, I would try to get the modules compliant and then do the templates.

Now there is another way to do this with little issues (coders correct me if I'm wrong as It's only theory) you can run the gavick templates and any application that uses 1.2 if you can run them both in no-conflict and add a script to load 1.2 from google API after Gavicks Mootools. This way you don't have to upgrade the Gavick templates or modules and still run the forum with 1.2 full on. Sloppy I know but if your just loading the forum and modules, it would get you through until the templates are updated.

Hi

I got some news in this topic:

Problem will be solved with nearest update when all T3-based templates will be
compatible with the MooTools 1.2.*

Thanks. At least that's something to look forward to.