Question Kunena 1.0.10 pre-release for template designers

Kunena 1.0.10 is now in final testing and I would like to give it to all template designers before it will be released. I will also answer questions regarding to it.

Default_ex template has seen huge amount of small fixes, most notable is removal of most PHP notices. There has also been some minor interface changes, for example in CKunenaConfig. Global is still there, but I recommend you to use $fbConfig =& CKunenaConfig::getInstance(); instead of using globals. Same is true for: $fbSession =& CKunenaSession::getInstance(), which is defined in lib/kunena.session.class.php . Moving to ::getInstance() instead of global fixes some issues..

If you want a copy of Kunena 1.0.10(PRE), please send me PM. Remember to tell name(s) of your template(s), was it based on default or default_ex and perhaps an URL pointing to it.

I would also like to have reports if your theme works without any (or with only few) changes in Kunena 1.0.10.

is this same for 1.51b. i mean if we made a template for v1.51, will it support at v1.5 stable? or 1.0.10 follows a different roadmap?

No, 1.5 branch has been obviously adapted to j1.5 so some things had to be renamed, all changes in 1.0.10 are there, but also extra changes.

If you want to do a 1.5 template, please send same message to matias, and specify you want it to be for 1.5, although, as 1.0 is our current stable release, you will be accepting also to do the 1.0.10 version

Our current internal 1.5 build is 1.5.2b, if things keep going as they are now, it will be our last release before 1.5.3RC

actually as you mentioned before, it is really complex creating a template for kunena cos of php files. it is really difficult to update skins for new versions. will this be change at the future releases. i mean, will it be more css based template structure?

Yes, but will take some time, our plans from day one include the creation of a simplified template structure and and API for it, but obviously, there are issues with bigger priority, nativeness, performance and stability... after taht, we follow our ideas, and the community desires in uservoice

But the new template API is definitelly on our pipeline, both template and plugins APIs

I'm sorry about the silence, but I've run out of hours while fixing several bugs every day for K1.0.10 and K1.5.2. We had to get most known bugs fixed before Thursday, mostly because of our personal agenda.

There were also so many issues found in the testing that giving out a week old version would have been badly deprecated by now.

As 1.0.10 will be the last K1.0 release, I advice template designers to use it as base of your new or updated templates. This is because template files contain huge amount of bug fixes and even some security fixes.