×
Kunena 5.2.6 released and Blue eagle 1.6.6 released (25 Jul 2021)

The Kunena team has announce the arrival of Kunena 5.2.6 [K 5.2.6] which is now available for download as a native Joomla extension for J! 3.9.x. This version addresses most of the issues that were discovered in K 5.2 and issues discovered during the development stages of K 5.2.6

× Topics that are moved into this category are generally considered to be closed. Users may want to add additional information but these topics should not be resurrected in order to discuss new problems or unrelated matters.

Question BBCode editor / Quick Reply not working (and other JavaScript issues)

More
10 years 11 months ago - 10 years 11 months ago #1 by Matias
If BBCode editor is not working, you have a JavaScript conflict or error in your site.

It usually means that you have installed a template, plugin or module that tries to load its own JavaScript library which is not compatible with Mootools 1.2.

Or you may have broken JavaScript somewhere in your page -- especially IE is very sensitive to the smallest errors and just gives up when it sees a potential problem.

How to debug it?

Following instructions are for existing site, but sometimes it could be easier to create a new site and install extenstions into it one by one -- first installing Kunena.

1) Read error message

If you get a error message, please read it. Even if you cannot understand all of it, it's usually written in good English (or in your language) and does contain information (like filename) which helps you to find out which extension is causing the error.

2) Show source code from the page (HTML)

Usually the easiest way to solve JavaScript issues in your site starts with a quick look into HTML source code. Even if it may sound frightening, it's actually pretty simple task that can be done by using your browser. It doesn't matter if you don't know how to read HTML either -- we are just trying to find simple patterns from it.

When you open HTML source code (right click to the page and choose show source / HTML) you will see something like this:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="https://www.w3.org/1999/xhtml" xml:lang="fi-fi" lang="fi-fi" >
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8" />
  <meta name="robots" content="index, follow" />
  <meta name="keywords" content="..." />
  <meta name="description" content="..." />
  <meta name="generator" content="..." />
  <title>Forum</title>
  <link href="/templates/rhuk_milkyway/favicon.ico" rel="shortcut icon" type="image/x-icon" />
 
  <link rel="stylesheet" href="https://kunena16/components/com_kunena/template/default/css/kunena.forum.css" type="text/css" />
  <style type="text/css">
    <!--
	/* Kunena Custom CSS */
	...
	/* End of Kunena Custom CSS */
    -->
  </style>
  <script type="text/javascript" src="/plugins/system/mtupgrade/mootools.js"></script>
  <script type="text/javascript" src="/components/com_kunena/js/slimbox/slimbox.js"></script>
  <script type="text/javascript" src="/components/com_kunena/template/default/js/default.js"></script>
 
<link rel="stylesheet" href="/templates/system/css/system.css" type="text/css" />
 
<link rel="stylesheet" href="/templates/system/css/general.css" type="text/css" />
<link rel="stylesheet" href="/templates/rhuk_milkyway/css/template.css" type="text/css" />
<link rel="stylesheet" href="/templates/rhuk_milkyway/css/blue.css" type="text/css" />
<link rel="stylesheet" href="/templates/rhuk_milkyway/css/blue_bg.css" type="text/css" />
<!--[if lte IE 6]>
<link href="/templates/rhuk_milkyway/css/ieonly.css" rel="stylesheet" type="text/css" />
<![endif]-->
 
</head>
<body>
...
</body>
</html>

Usually <head> contains a lot of more data, but the basic structure is always the same.

Source code may look complicated, but the only lines we are interested in are like this:
<script type="text/javascript" src="..."></script>

Just collect all of them together like this (using the example above) -- just be sure that you get them all (use search) as they may not be in one place:
<script type="text/javascript" src="/plugins/system/mtupgrade/mootools.js"></script>
  <script type="text/javascript" src="/components/com_kunena/js/slimbox/slimbox.js"></script>
  <script type="text/javascript" src="/components/com_kunena/template/default/js/default.js"></script>

In those lines we are only interested in paths and filenames (althought some of the lines may contain full URLs).

3) Check that Mootools 1.2 is loaded

First check that the list contains /plugins/system/mtupgrade/mootools.js (Joomla 1.5 only). It's very important that this file is loaded, as our JavaScript doesn't work without it. If the file is not in there:
  1. Check that Administration >> Extensions >> Plugin Manager >> System - Mootools Upgrade is Enabled
  2. If it is enabled, you have badly behaving extension that removes Mootools from the page. Go to next step.

4) Find out which extensions are loading JavaScript

All the paths contain information that can be used to find out the extension which is causing the conflict. Paths always contain one of these folders:
  • /administration: Administration -- you should never have these
  • /components/com_xxx: Component named xxx
  • /libraries: Joomla
  • /media/system: Joomla
  • /media/xxx: Usually extension named xxx
  • /modules/mod_xxx: Module named xxx
  • /plugins/yyy/xxx: yyy/xxx plugin (system/mtupgrade)
  • /templates/xxx:Template named xxx

You can use above list to find the extensions that are loading JavaScript. Usually one of them is causing the issue, which greatly helps in finding the root cause of your problems.

Please note that those names are only the directory names from the extenstions -- they are not the names you usually see when you're in your backend. Usually they are named closely after the real name, but not always. For example com_community is JomSocial and com_comprofiler is Community Builder (both of with works perfectly with K1.6). So you may need to use Google or take a look into those files to find out the extension.

5) Disable all extensions which are loading JavaScript

Please write down every action you do so that you can restore your site into previous state. You may do these steps one by one and look if the issue is fixed, or do it all.
  1. All Joomla and Kunena JavaScript is safe to use
  2. If your template is listed, change it to rhuk_milkyway
  3. If a plugin is listed, Disable it
  4. If a module is listed, Disable it
  5. If a component is listed, find all of its modules and plugins and Disable them

Then go and check if the issue has been fixed. Usually Kunena should be working just fine after this step.

If not, look if you still have JavaScript loaded by one of the extensions.

6) Find out what is causing the issue

At this point you should have working Kunena BBCode Editor.

Now you do the previous steps in reverse order and put template / plugins / modules back one by one. Every time you should take a look if the issue has been fixed. Eventually you will find all the extensions which are incompatible with Kunena.
Last edit: 10 years 11 months ago by Matias.
The following user(s) said Thank You: fxstein, thezone
The topic has been locked.
More
10 years 11 months ago #2 by Matias
Here are some proposals by our users, how to fix Mootools issues:

----

* If you're having issues with RocketTheme templates, drackmania proposes this solution:

In the Joomla administration panel go to Extensions -> Plugins -> System - RokBox and activate the option "Use Legacy Parameters"

----

* If you get message: Kunena: You have a plugin that uses Mootools 1.1 or custom version of JHTMLBehavior...

In the Joomla administration panel go to Extensions -> Plugins and find System - Mootools Upgrade. Make sure that it's listed as first System plugin.
The topic has been locked.
  • Not Allowed: to create new topic.
  • Not Allowed: to reply.
  • Not Allowed: to edit your message.
Time to create page: 0.070 seconds