Not same thing though as NEVER permission.
Yes, see it now. You just don't set anything for it. So works same way then really.
Yes, see it now. You just don't set anything for it. So works same way then really.
Ok, I did it. My first XF conversion
- Thread starter Joeychgo
- Start date
Well it was different when I used phpBB 3.1. That actually uses exact same permission system (inherits). lol, but it actually will override a Yes with a No. So there was no need to set main usergroup as mostly No or (Not Set), because a custom usergroup could still override the Yes with a No.
Bring back the simple vBulletin 3 permission days. When each group didn't inherit from another group and simplified things. I'm not surprised a lot of people (especially new forum owners), or those coming from using vBulletin 3 e.t.c. They don't understand it at first.
Bring back the simple vBulletin 3 permission days. When each group didn't inherit from another group and simplified things. I'm not surprised a lot of people (especially new forum owners), or those coming from using vBulletin 3 e.t.c. They don't understand it at first.
- Thread starter
- Moderator
- #44
- Joined
- Feb 28, 2004
- Messages
- 7,028
Its just unnecessarily complicated IMO. I don't see why it has to be as such...
- Thread starter
- Moderator
- #45
- Joined
- Feb 28, 2004
- Messages
- 7,028
Perfect example... I just locked myself out of my moderator forum, and I have no idea how
- Joined
- Jul 9, 2006
- Messages
- 20,983
WOW!!!! Never thought I'd see that happen. Last we chatted about the migration idea - you were considering IPB.
First wanted to say CONGRATS! How'd you rate the migration experience and has been a painful/painless as you thought it would be?
Second = quite impressive your theme port! It's pretty damn close to exact from what I can see via the wayback machine. Only - it's such a cleaner styling. Of course - XF is just a much cleaner script all-around imo - so that helps. Did you augment one of the PixelExit themes or are they working on that for you? Whatever the case = job well done!
Um........ How exactly did you do that? Didn't think that was even possible
J.
Guessing you denied default users group from seeing, or entering that forum. And mods, admins and custom groups added will inherit the same permission unless you add them to same forum also and change permission to Yes for them allowing it - that you changed and ticked No for users group for that forum.
Any forum you add default users group to and change permission from Yes to No, means you also need add other groups that inherit permission from it and change them to Yes to override default users group. Otherwise they take the No permission from them if permission is 'Not SET' for that usergoup - meaning it takes it from default group.
Last edited:
Because in a way the permission system is more powerful than vBulletin 3. With vB3 you only had guest group that covered both Bots/Guests together. So if you allowed guest posting (it was also allowed for bots). With WBB you have EVERYONE group and Guests. So if you denied Everyone group from posting and allowed guests to posts. Bots are actually blocked different from guests.
That is not something you could ever do with vB3 because guests and bots got treated with same permission group. But agree, it is complicated and has become same inheritance permission system as phpBB3 for both XF and WBB. That people say they hate so much about phpBB3, lmao!
Last edited:
- Thread starter
- Moderator
- #49
- Joined
- Feb 28, 2004
- Messages
- 7,028
Well, to be frank, it came down to a few factors. Cost was one; I also didn't see a lot of activity on IPB forums; I didn't see much in the way of custom programming availability; IPB isnt really widely used; In the end, it really came down to one thing. The overall feel and impression I have is that IPB seems pretty arrogant to me overall. Conversely, Most of the XF people I've come across remind me of the old VB days, where there are plenty of people willing to help and go above and beyond.
The actual migration was painless, albeit this was a small site. Bigger problem is just finding my way around things. As I've discussed in this thread, there are a few things such as permissions, that are IMO unnecessarily complicated. I have 13+ years experience running multiple forums, and if am getting confused, I can only imagine how it can confuse a first time admin.
Steve from PixelEdit did it for me. He's great to work with and not terribly expensive. I highly recommend him for everyone else. Poor guy doesn't realize he just became my go to guy for styling stuff.
I use this skin on a few sites, and the idea was to make the transition as minimal for members as possible. Familiarity makes things easier on the members who have to learn new ways to do things. (something I fought for here at TAZ when we converted)
Um........ How exactly did you do that? Didn't think that was even possible
I'm not 100% sure.
- Joined
- Sep 14, 2012
- Messages
- 5,034
- Joined
- Jul 13, 2004
- Messages
- 3,451
Joeychgo If nobody has mentioned it already, be sure to also check out the ACP options for testing perms.
- ACP => Users => Analyze Permissions => {User Name} <-- This will allow you to enter a user name and view all of the calculated permissions for the user account.
- ACP => Users => Test Permissions => {User Name} <-- This will allow you to enter a user name and view the site mimicking the user account. When done you can click the link in the upper-right to revert back to your own permissions.
- Thread starter
- Moderator
- #52
- Joined
- Feb 28, 2004
- Messages
- 7,028
Well, the problem first was I couldn't see the mod forum, then I discovered the mods couldn't either.
The problem, I think, was that the forum permissions were set to "inherit"
What fixed it was when I took the mods (and myself) and made the primary usergroup as moderating and no secondary usergroup. If I did it the other way, with the primary as registered and the secondary as moderating - that's when they had no access to the forum
The problem, I think, was that the forum permissions were set to "inherit"
What fixed it was when I took the mods (and myself) and made the primary usergroup as moderating and no secondary usergroup. If I did it the other way, with the primary as registered and the secondary as moderating - that's when they had no access to the forum
- Joined
- Jul 13, 2004
- Messages
- 3,451
By any chance were you trying to flag the forum as "Never" for the normal registered group to restrict access to it?
- Joined
- Jul 8, 2014
- Messages
- 424
Joeychgo I'm confused, your title says TAZ Admin, so weren't you in on the TAZ transition, or have access to the TAZ ACP?
As for the permissions issue, you really should have all registered users in the Registered usergroup as primary ad Mod as secondary.
Then pick a mod and use the Analyze Permissions tool, selecting the mod user and the forum in question and see what is tripping up access.
You have usergroup permissions that apply across the entire forum in general, and then Node permissions which can override this.
Example: I have forums that are for paying members only. I have the node permissions on these categories set for guest/registered to view node = "allow" but View threads by others / View thread content / Post new thread / Post replies = "revoke". This negates the usergroup Allow, for this node. So they can see that the sub-forums exist, but they can't see any thread, content, previews, nothing. Then I have the paid member group se to Allow the view/post permissions, which overrides the Revoke as that is a lower tiered usergroup permission within the node.
It took some doing to get that figured out. I didn't have "post new thread = revoke" set and one registered user was able to post a new thread in the paid members forum, but of course, she couldn't see her thread right after she posted it.
As for the permissions issue, you really should have all registered users in the Registered usergroup as primary ad Mod as secondary.
Then pick a mod and use the Analyze Permissions tool, selecting the mod user and the forum in question and see what is tripping up access.
You have usergroup permissions that apply across the entire forum in general, and then Node permissions which can override this.
Example: I have forums that are for paying members only. I have the node permissions on these categories set for guest/registered to view node = "allow" but View threads by others / View thread content / Post new thread / Post replies = "revoke". This negates the usergroup Allow, for this node. So they can see that the sub-forums exist, but they can't see any thread, content, previews, nothing. Then I have the paid member group se to Allow the view/post permissions, which overrides the Revoke as that is a lower tiered usergroup permission within the node.
It took some doing to get that figured out. I didn't have "post new thread = revoke" set and one registered user was able to post a new thread in the paid members forum, but of course, she couldn't see her thread right after she posted it.
- Joined
- Jul 8, 2014
- Messages
- 424
Yeah, never should not be used unless you want to create a "they were naughty" group and restrict access for that person, short of banning them, because nothing will override a never.
If registered group had a never, and then mod was secondary, the never overrides all. So if you made mod primary and no secondary, the never wouldn't come into play.
Use the Revoke instead, at the node level
Did you add Users default group to the Mod Forum and set No (and not NEVER) for that group to view it? If you did, then you also need to add Mod and Admin group to the forum also and for same View permisson. Set it as Yes, that will override the Users group being set as No for that forum on same permission. But if you only have Users group added to the forum then Admin and Mod groups are going to inherit the No permission until you add both other staff groups
- Joined
- Jul 8, 2014
- Messages
- 424
Setting No (not set) is inherit. That doesn't work, they'll still see it.
If you want to hide a node so that only mods can see, it, you have to set View Node = Revoke for guests and registered (both groups) then make sure everyone is in the Registered group (everyone, even banned members), and then for the Mod group you set View Node = Yes.
This way no one outside of the Mod group will ever even see the node, because their (user group level) permission is revoked, and this is only overridden by the Allow.
This also assumes that your styling priority is set up properly (i.e. mod group is a higher priority than registered/guest)
If you want to hide a node so that only mods can see, it, you have to set View Node = Revoke for guests and registered (both groups) then make sure everyone is in the Registered group (everyone, even banned members), and then for the Mod group you set View Node = Yes.
This way no one outside of the Mod group will ever even see the node, because their (user group level) permission is revoked, and this is only overridden by the Allow.
This also assumes that your styling priority is set up properly (i.e. mod group is a higher priority than registered/guest)
- Joined
- Jul 8, 2014
- Messages
- 424
GTB this might be a difference between WBB and XF. You don't add groups to nodes, all groups are already given a permission set for every node. I don't know WBB at all I'm just guessing...
No, you are right. I overlooked that a No permission doesn't override a Yes permisson so there's no need to add Admin and Mod groups. Or that at least would be the case for WBB. And forgot that XenForo has that other forum setting for when you use things like staff forums.
Actually, scrap that as well. I just looked at my own forum permissions for my guest forum with Users group added to Deny starting topics and notice I did need to add Admin group and allow them to start topics otherwise they couldn't. So the No did override the Yes
Actually, scrap that as well. I just looked at my own forum permissions for my guest forum with Users group added to Deny starting topics and notice I did need to add Admin group and allow them to start topics otherwise they couldn't. So the No did override the Yes
Last edited:
- Joined
- Jul 13, 2004
- Messages
- 3,451
You don't have to revoke any permissions to make a node that only certain groups can see.
In the example of a staff node/forum, flag the node as "Private node" and that automatically prevents any group from seeing it unless they group (eg: staff members group) has been given the explicit "View" node permission.
In other words, if a node if flagged as private then being able to see the node becomes an 'opt in' setting per group instead of having to 'opt out' specific groups.