Sticky If you are having problems with Kunena, please read this first

in firefox

you can see, mootools correct version, the same as in this forum

bbcode not visible

in chrome


in IE9

no problem...

What to do?

PS: in debugmode:

500 - JDatabaseMySQL::query: 1146 - Table 'juneart.jos_tagmeta' doesn't exist SQL=SELECT * FROM jos_tagmeta WHERE ('/forum/2-rabochij-forum/1-raschet-czen' REGEXP uri)>0 and published='1' ORDER BY ordering

disable plugin system tag meta and error disappeared

Early diagnosis of potential problem situations

Kunena 1.6.4

From K 1.6.4, Kunena debug mode gives some early indication of Javascript issues that have been reported by users. When you run debug, you will be alerted to the following issues.

Mootools is not loaded
The version of Mootools is not compatible with Kunena
Mootools DOMready event does not work

In addition, the plugin load order is not necessary to overcome conflicts between Mootools and other frameworks like jQuery or conflicts with old Joomla site templates and plugins. These issues were mainly experienced in releases before K 1.6.4. Kunena 1.6.4 also fixes a number of the issues discussed later in this article.

debug enabled.
none of the above does not appear in firefox

I WIN!!!!!
Error mootools 'Redeclaration of var gecko'

mootools.js change code

window.__defineGetter__("gecko",function()

on

window.__defineGetter__("gecko1",function()

:woohoo:

Daser wrote: I WIN!!!!!
Error mootools 'Redeclaration of var gecko'

mootools.js change code

window.__defineGetter__("gecko",function()

on

window.__defineGetter__("gecko1",function()

:woohoo:

Never seen that before :ohmy: :ohmy:

But it work's!!!

The situation arising in the issue reported by Daser is, whatever the solution, related to Mootools.

Gecko is primarily used in web browsers, the earliest being Netscape 6 and Mozilla Application Suite (later renamed SeaMonkey). It is also used in other Mozilla web browser derivatives such as Firefox, Camino, Flock, K-Meleon and the version of Internet Explorer that runs under Wine. Therefore, if you change the Mootools definition from "gecko" to "gecko1" what this basically says is "disable the JHTML behaviour as far as Firefox is concerned". Put this another way, this indirectly explains why people may not see the kind of problem described by Daser in Google Chrome but they may see the issue if they use some version(s) of Firefox.

In the final analysis, the Mootools 1.2.5 Javascript library was not developed by Kunena but we have not seen the problems just mentioned with Firefox. What would be beneficial is to report this issue to the Mootools development team .