Question Joomla 6 support?

Ok, one thing that is already long time on my wish list is the Kunena Configuration.
This is implemented as a view (with model and controller), the reason is probably due to limitations in the past.
I would like to convert that to 'real' component options like every other component in Joomla has.

The functionality of how the config options will be used in the code will remain the same using the KunenaConfig class, so no changes needed there.

This would make the developers life a lot easier:

• new users expect configuration under options
• functionality is build upon core joomla default config.xml
• adding an option is as simple as adding a field, no more adding things in multiple places in the config MVC (and no more deprecated messages when missed a setting)
• a lot of code can then be removed, making maintenance easier
• etc.

Using JS we could even have the current functionality of highlighting fields whose value is not the same as the default value.
This is a lot of work, but doable before 7.0 release.
Is that something I can pursue or am I the only one who would like to have this / are there other reasons I do not know why we do not do it this way?
 
 

I would like to have this now you only see the rights.

I'm trying to add a user avatar in Kunena 7.0 using a clean install.
But I'm missing the avatar tab in the profile edit.
Even when I upgrade an existing forum, I don't see the avatar tab.
But the old avatars are still displayed.on the front
ps
the Gravatar integration works well
 

Leen wrote:

I'm trying to add a user avatar in Kunena 7.0 using a clean install.
But I'm missing the avatar tab in the profile edit.
Even when I upgrade an existing forum, I don't see the avatar tab.
But the old avatars are still displayed.on the front
ps
the Gravatar integration works well

 

Good catch! > github.com/Kunena/Kunena-Forum/pull/9919

ruud wrote:

xillibit wrote:

Hi,

The plugin search is like the search tab from kunena menu by display it anywhere else outside of Kunena. Since finder it isn't usefull now



 

Okay, so I guess it can be 'archived' then? I will not refactor it for Joomla 6

yes this can be archived

ruud wrote:

Ok, one thing that is already long time on my wish list is the Kunena Configuration.
This is implemented as a view (with model and controller), the reason is probably due to limitations in the past.
I would like to convert that to 'real' component options like every other component in Joomla has.

The functionality of how the config options will be used in the code will remain the same using the KunenaConfig class, so no changes needed there.

This would make the developers life a lot easier:

• new users expect configuration under options
• functionality is build upon core joomla default config.xml
• adding an option is as simple as adding a field, no more adding things in multiple places in the config MVC (and no more deprecated messages when missed a setting)
• a lot of code can then be removed, making maintenance easier
• etc.

Using JS we could even have the current functionality of highlighting fields whose value is not the same as the default value.
This is a lot of work, but doable before 7.0 release.
Is that something I can pursue or am I the only one who would like to have this / are there other reasons I do not know why we do not do it this way?
 

 

Good idea to do it if it can simplify the update process and others parts, it wasn't in the mind or forgotten

xillibit wrote:

yes this can be archived
Good idea to do it if it can simplify the update process and others parts, it wasn't in the mind or forgotten
 

I will leave the archiving to you @xillibit as you probably have a folder or repository to move this to
As for the configuration: top! Will start working on this, this will take a little bit longer

@Leen Are you using Kunena Discuss? I'm looking for a tester of this:  github.com/Kunena/Kunena-Addons/pull/324

If needed I can mail you a test installation package, just let me know if you have time and energy to look at this.