Important 1.5.9 - Known issues

Here is the list of issues and/or problems that I have discovered with K 1.5.9. This list is not 100% complete and it's not an official list, either:

1. The old Fireboard-style templates are installed when users upgrade from K 1.5.7 or earlier.
   • See discussion There is only one endorsed and supported Kunena template
   • The old templates (default_gray, default_green, default_red) will be *removed* in K1.6.
2. Search queries containing quoted strings are truncated

• This issue has not been resolved.

Quote button to reply to a post truncates the subject if the subject contains quotation marks

• See discussion K 1.5.8: Using Quote"button" truncates Subject
• This matter has been addressed in K 1.6.

Built-in avatars do not display

• See discussion Avatar not display in Kunena 1.5.9
• There is a workaround for this issue.

Community Builder avatars are too large for the display

• See discussion Problem with Kunena 1.5.8 + CB Avatar
• There is a simple workaround for this.

Apart from the long-standing matters involving "threaded" vs. "flat" discussions and the moderators "split/merge" functions (which have been disabled for a long time), that's it; there are only these five areas where Kunena does not behave as you might expect ... and none of them are serious enough to prevent you from upgrading from an older version to the latest release!

As far as I can tell, the dozens of other reported "problems" have all resulted from peculiar instances of web hosting policies, conflicts with other Joomla extensions, requests for new features that have not been implemented or users' unfamiliarity with (or misuse of) Kunena's control mechanisms.

There is a known issue with the Kunena search function.

Searches containing the following characters will not return any results:

+ - ' "

If you post a new topic in a discussion and assign a topic icon to it but later edit that message, unless you reassign the topic icon, the topic icon will be "lost" when it is resubmitted to the forum. This is a known behaviour in K 1.5.x that will be addressed in K 1.6.