- Posts: 1
- Thank you received: 0
Kunena 7.0.4 Released
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.
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.
Question K 1.0 / K 1.5: Read this if you are template designer
16 years 1 week ago - 15 years 10 months ago #46331
by sozzled
Blue Eagle vs. Crypsis reference guide
Read my blog and
Replied by sozzled on topic Re: K 1.0 / K 1.5: Read this if you are template designer
This discussion topic started about 12 months ago by announcing that there would be no further support offered for the old Fireboard-style templates in Kunena. The result of this is that there has been a new policy direction:
There is only one endorsed and supported Kunena template ... default_ex
.
This topic has argued for and against the combination of CSS and PHP code - a clumsy technique technique, at best, originating in Fireboard - which has survived into the current release of Kunena 1.5. This combination of CSS and PHP has resulted in an enormous number of queries and it probably accounts for the single largest problem area within Kunena today.
The number one problem in Kunena is that user-developers lose interest and do not keep their template designs updated when new versions of Kunena are released.
Fortunately, this problem should mostly go away in K 1.6 mostly because the K 1.5 templates are completely incompatible with the new version. Users who want to retain their K 1.5 template "look" will need to support one another to develop a workable solution. I believe we will receive a lot of questions that will go like this: "I updated to K 1.6 but now I can't use the customised K 1.5 template that worked perfectly in K 1.5. Can I go back to K 1.5?" The answer is, no, once you update to K 1.6 there is no going back.
This will lead, inevitably, to the next question: "OK, so I can't go back to K 1.5. Can you please change the default template so that it works in my site?" Well ... that's something for template designers to think about.
However, I think that this discussion topic, that started nearly a year ago and that focused on the design problems facing the developers of K 1.5, has now outlived its usefulness and should probably be closed.
This topic has argued for and against the combination of CSS and PHP code - a clumsy technique technique, at best, originating in Fireboard - which has survived into the current release of Kunena 1.5. This combination of CSS and PHP has resulted in an enormous number of queries and it probably accounts for the single largest problem area within Kunena today.
The number one problem in Kunena is that user-developers lose interest and do not keep their template designs updated when new versions of Kunena are released.
Fortunately, this problem should mostly go away in K 1.6 mostly because the K 1.5 templates are completely incompatible with the new version. Users who want to retain their K 1.5 template "look" will need to support one another to develop a workable solution. I believe we will receive a lot of questions that will go like this: "I updated to K 1.6 but now I can't use the customised K 1.5 template that worked perfectly in K 1.5. Can I go back to K 1.5?" The answer is, no, once you update to K 1.6 there is no going back.
This will lead, inevitably, to the next question: "OK, so I can't go back to K 1.5. Can you please change the default template so that it works in my site?" Well ... that's something for template designers to think about.
However, I think that this discussion topic, that started nearly a year ago and that focused on the design problems facing the developers of K 1.5, has now outlived its usefulness and should probably be closed.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Last edit: 15 years 10 months ago by sozzled.
Please Log in or Create an account to join the conversation.
Time to create page: 0.237 seconds