Kunena 6.2.5 & module Kunena Latest 6.0.7 released

The Kunena team has announce the arrival of Kunena 6.2.5 [K 6.2.5] which is now available for download as a native Joomla extension for J! 4.3.x/4.4.x/5.0.x. This version addresses most of the issues that were discovered in K 6.1 / K 6.2 and issues discovered during the last development stages of K 6.2

If you are having problems then, for your own benefit, it would save us all a lot of time if you would kindly post your configuration report when you ask for help from this forum. If you do not post your configuration report we will not ask you for it but you will probably not get your problem solved, either.

K 2.0 support will cease on 31 August 2013 and this section of the forum will be closed and archived after that time and no further questions will be answered about this version.

Question When all else fails, try this

More
11 years 8 months ago - 11 years 8 months ago #1 by sozzled
The information in this topic applies to all versions of Joomla.

We often read "Kunena does not work in Joomla x.y.z" or "something doesn't work in Kunena" and we then look at www.kunena.org and cannot reproduce the problem - and we haven't done anything special at this website! No matter how often we try to tell people of the need to evaluate Kunena in a test environment, they seem reluctant to do this. We're then left trying to figure out what people did before they installed Kunena and why they may be having the problems that they're now having.

There is a much simpler way that people can find out if Kunena will work for them or not. This is how it's done:

(1) On the same platform as where your live site will operate, create a completely new "vanilla-flavoured" Joomla test site (it doesn't matter if you use J! 1.5.26 or J! 2.5.4 for this test). On this test site, do not install anything else. Do not install any other templates, or extensions like sh404SEF or Community Builder for example.

(2) Using this test site, install the version of Kunena that you had problems using in your production environment. Do not change any of the original configuration.

(3) With this very simple test site, run the same tests that resulted in problems in your production environment. Does the original problem occur in this test site? If everything works then you have found the answer to all of your problems. You now have a working website! :woohoo:

(4) One by one, change your test site by adding the other extensions you have on your problem site. After adding each extension, continue to test Kunena to make sure that you do not have any problems. Either you will find something that you've added which caused the problem (and then you can fix it up or remove it from your live site) or you won't. If you don't find the problem on your test site then (again) you now have a site that works! And then you can use this working site instead of the one that you've got problems with.

The first three steps in this process should take less than one hour.
Last edit: 11 years 8 months ago by sozzled.
The following user(s) said Thank You: Nemo10, Maszek, MfGLucker, valimazarescu
The topic has been locked.
Time to create page: 0.390 seconds