Merged [Merged topic] New topic / wrong category

A big thank you to the mods for placing my post here. One solution is to have a back end function which enables admins/mods to disable any categories contained in the drop-down list that are locked to be accessible to admins/mods and above only. Meantime, I am going to have to reorder the forum so that the most used category/section is shown (Like Sozzled suggests). It's not very clean, but it will have to do until we find a better way forward.

Azure wrote: I am having problems where new posts are created by users when they don't first select the right category to post in. This is an extra step to the process of posting a new topic from previous versions of Kunena and like most things in life, people get used to doing things a certain way.

Consequently, they fail to select the right category and it gets chucked in the first one which happens to be a locked topic containing the rules of the forum. The result is that anyone below moderator level can read the post but cannot join in the debate.

Is there any way to alter the drop down list so that it at least only shows unlocked topics, thus at least avoiding the scenario of starting a discussion and only mods and above being able to reply to these topics?

Screenshot provided as my explanation is often insufficient to spark a response.

Hi, I have the issue that has been discussed before here on kunena, and that is where the first category that defaults to be the category for new topics is not a locked category and so most users (are either too lazy or unaware that they need to select a category) put their new topic in the first category.

fxstein, asked for suggestions www.kunena.org/forum/5-General-Talk-abou...wrong-category#70314

and my wish would be to be able to have no category to default and so they must select a category. This way they actually have to think about which category they need to put their topic in.

So in the drop down list would look like:
- Select Category -
Category 1
Category 2
Category 3

thanks

This feature is already in the K2.0. version. beta will be released this week.