Question Kunena 1.6 - a moderator's view

don't get your hopes up, ETA on release is soon. But expect around summer 2011.

Today's preview contains a few screenshots of the new Kunena user profile feature. I've marked a couple of special features (the location of the edit link and the new tabbed dislay) in the following image:



Editing the user profile is done in a similar way to the Kunena configuration settings that I discussed a couple of messages ago. The user settings are arranged in 4 tabbed "panes" as the following screenshots illustrate:

1. User Account
2. Profile Information
3. Avatar Image
4. Forum Settings

The images shown here are based on a work-in-progress. They are not intended to be an official endorsement of what the finished product will look like, nor do they represent the default values or imply any recommended values, with the finished product. They are merely an illustration of what people may encounter with the new version.

Very neat, I do like it.

Just one little question: where's the "moderate user" section?
I mean the part where a user or an IP can be banned and his posts deleted.
In some older screenshot I remember we could find it in the user profile... maybe simply temporarily removed due to work in progress?

I can never congratulate enough with Kunena team.

Good question, MarkBoy81. I'll put together some screenshots tomorrow and post them here.

You cannot moderate yourself..

But that screen is not yet finished and still needs some work to be more useful.

We had an interesting discussion recently - K 1.5.11: 'change username' javascript popup issue - in which an issue emerged that has not been properly addressed for a long time. How do you handle a username change (assuming you allow it) if a user wants to change theirs to one that's already being used?

In K 1.5 this results in an [Javascript] alert and the result is a mess! The alert is unnecessary: there's no real need for a user to "confirm" anything. The following screenshot shows one example of how the situation has been eliminated in K 1.6. The scenario is user test-user3 wants to change their username to test-user2 (which is being used by someone else); after clicking the Submit button, the message at the top of the screen informs the user that their request was not allowed.