Question Moderation

Thanks for the quick response. I have made those changes.
As for the users, they are all identical, nothing special for end users...

The category looks like:
Access Control: User Groups
Primary User Group: Registered
Include Children: Yes
Secondary User Group: Registered
Include Children: Yes
User Group Allowed to Post: Registered (and sub groups)
User Group Allowed to Reply: Registered (and sub groups)
Locked: No
Review Posts: No
Allow Anonymous: No
Post Replies As: Registered
Allow Polls: No
No moderators assigned.

Not sure what else to look for...???

As I wrote, earlier (in reply to your opening comment):

rlstephens wrote: I have a ... category that is set to no moderation. Some users are able to post, others require moderator approval.

The key to solving this mystery is to figure out what's different in that one category between those who can post without requiring moderator approval against those who need their messages approved.

What rich wrote would apply to all new users on all categories (not the one category that you are having problems with).

When I look at your configuration report, you appear to have the correct (default) setting:

Configuration » Security » Security Settings » Moderate New Users = 0

That's what rich was talking about.

If the same users - those who need their messages approved - are able to post in other categories on your forum and not require their messages approved in other categories then the global configuration setting I've mentioned should have no effect. Can you confirm that the issue is isolated to only the one category you mentioned in your opening post?

Thanks All.
I've applied the changes recommended from the other post as well. It appears it could be related to first time posters, which that setting was set to "0" (thinking that meant never)...

I do have 2 global moderators...

Will watch for a while...

Robert

rlstephens wrote: I've applied the changes recommended from the other post as well. It appears it could be related to first time posters, which that setting was set to "0" (thinking that meant never)

Well, yes, 0 means "never". What this value actually means is,

... a number of posts [on a user-by-user basis]. If the user has less posts than specified in this field, all his messages are marked to be reviewed by moderators prior to publishing.

Therefore, if a user has made no posts then that person does not require their first message to be approved by a moderator. If the value is 1 (and a user has made no posts) then that person will require their first message to be approved by a moderator. If the value is 2, then the first two posts, and so on and so on.

Remember, if you set this value higher than zero, all the user's messages will require moderator review until the total number of messages posted by that user has reached this value. If a user still has messages waiting moderator review action, this can affect the "problem".

The real question, however, is what happens with first-time users who post in other categories that are similarly configured with Review Posts = No (as your "For Sale" category is currently configured).

You have mentioned (a couple of times in this topic) that you have 2 global moderators. I am not sure what is important about this fact but thank you for telling us.

The other post mentioned that "0" wasnt working correctly as described, so setting it to "" (blank) seemed to fix that. Thats what I did.

The re-post about 2 global mod's was more of a point of difference for the other post.

Sorry for the seemingly cross post.

Thanks again for all the help, will see if it's fixed now.
Robert

rlstephens wrote: The other post mentioned that "0" wasnt working correctly as described, so setting it to "" (blank) seemed to fix that.

Hmmm ... if the setting needs to be "" (null, not blank) and this is reported in the configuration settings as zero then that's a problem for the developers to look at. If the setting the value to zero doesn't work then that's another problem for the developers to look at. If the setting has to be "" (i.e. null) for this to work then it would be surprising because, when people first install Kunena, the initial/default value is zero. If you change it, and then change it back to zero, but now you have to set it to "" (for things to work) you have uncovered a defect in K 3.0.5 that would affect everyone and this needs to be fixed.

See what I mean?