The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0
This category contains miscellaneous, uncategorised user contributions, (templates, modules, plugins and hacks) relating to older versions of Kunena that are no longer supported.
This category may also contain a few topics relating to K 1.6 that may have been moved here possibly by mistake.
The topics in this category are for historical interest only. Owing to the structural differences between K 1.6 and K 1.7, these ideas in these topics will not work with later versions and, for that reason, the topics are locked.
Important
K 1.5 latest posts module - no longer supported or maintained. Do NOT use this with K 1.6!
I seem to be having trouble with 1.0.45 - none of the options seem to be saving. For example, display type (always using list), item format (even if I remove everything and only put in %S)
I seem to be having trouble with 1.0.45 - none of the options seem to be saving. For example, display type (always using list), item format (even if I remove everything and only put in %S)
Any ideas why?
Actually settings are saved by Joomla itself, there's only 1 xml file in my module which names all the parameters. That's all from module side. So try, if there isn't problem with other modules. You could try core Joomla modules. Looks like problem with Joomla itself.
The other Kunena latest posts module seems to work fine. The settings are saved etc. - for this module the settings are saved in the module itself (when I save/apply etc. the settings are still there in the backend), but they are not actually reflected in the module - the module looks default even after changing settings.
I wouldn't mind giving you an admin login to the site if you'd like to check it out for yourself.
The other Kunena latest posts module seems to work fine. The settings are saved etc. - for this module the settings are saved in the module itself (when I save/apply etc. the settings are still there in the backend), but they are not actually reflected in the module - the module looks default even after changing settings.
I wouldn't mind giving you an admin login to the site if you'd like to check it out for yourself.
Checked. Enabled cache 'holds' settings until cache expires. That's expected behavior. Disabling cache make changes visible immediately.
