The Kunena team has announce the arrival of Kunena 6.4.9 [K 6.4.9] in stable which is now available for download as a native Joomla extension for J! 5.0.x/5.1.x/5.2.x/5.3.x/5.4.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 6.4
The Kunena team has announce the arrival of Kunena 7.0.1 [K 7.0.1] in stable which is now available for download as a native Joomla extension for J! 5.0.x/5.1.x/5.2.x/5.3.x/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
Important note: Go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated. This is particularly necessary for major version jumps so that the table changes are adapted.
This category contains miscellaneous, uncategorised third-party extensions (e.g. JomSocial, Community Builder, etc.) 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, the ideas in these topics may not work with later versions and, for that reason, the topics are locked.
I'm fully aware that I'm not supposed to run a production host with display_errors = On in php.ini, but for the purposes of site development, I keep that option enabled to help solve problems that creep up.
Most components behave fine when this option is turned on. However Kunena throws a constant Notice at me on every page that could easily be resolved:
Notice: Undefined property: stdClass::$created_by in /path/to/host/plugins/content/sysplgaup_content.php on line 37 Notice: Undefined property: stdClass::$id in /path/to/host/plugins/content/sysplgaup_content.php on line 38
I had hoped that this would be fixed in 1.6.1, but it still isn't, so I'm reporting it here. This Notice does not show up when display_errors is set to Off, so it's not critical. But it seems like a quick and easy fix for the next version to help improve code compliance.