So when you have a forum and it’s set to “login required”, the “create new category” offers the choice between “all members” and “private”. When it’s not set to login required it changes to “public” and “private”.
However, in both situations the left button assigns everyone.
Now this happens:
I am setting up a new forum
I set it to login required because I’m still setting it up
I create a category and choose “all members”
It assigns everyone
I open up the forum to the public by disabling login required
The category is accessible for anonymous, non logged in, users
Panic
Expected:
when the button says “all members”, it assigns trust_level_0 or the fancy new logged_in_users.
Also, this made me realize that when the new granular permissions feature is enabled it does not apply to category permissions. Which is REALLY confusing.
Yes my intent was to not really change category permissions much with this upcoming change, so these (this and Category permissions and the new permission groups - #5 by martin ) are more unintended side effects. I don’t intend to remove everyone yet as an option from category permissions…but over time I think it’s probably a good idea to do a fast follow up on this.
The problem is that I was thinking it would be even less clear what I should migrate everyone category permissions to, but maybe it can follow logic like you are suggesting? E.g. if I remove everyone, a migration would add these category permissions for a site:
Site requires login → everyone becomes logged_in_users
Site is public/doesn’t require login → everyone becomes logged_in_users AND anonymous_users, two separate category permissions
I think this suggestion makes the most sense, and is the clearest, so I will make that change when I can.
