Flag Loggedin-only permissions

[Kirby]

XenForo treats logged out visitors ("Guests") and logged in but unconfirmed visitors ("Members") somewhat equal - they both get their permissions from usergroup Unregistered / Unconfirmed.

So when editing this usergroup there are many permissions like

• Use push notifiations
• Upload an avatar
• Upload a profile banner
• ...

that can (currently) only be applied to Members - they have no effect on Guests.

While it may be "logical" that some permissions can't be applied to guests, in some cases this is not so obvious and may cause confusion.

My suggestion is to make it more obvious that some permissions can't be applied to guests.

This could be achived (relatively easily) by adding a new flag Can be applied to loggedin users only to permission definitions:


With such a flag in place the edit usergroup permission controls ffor usergroup Unregistered / Unconfirmed could be easily improved, making it very clear that some permissions can only be applied to loggedin members:


Ideally the entity should also have an appropriate check method so 3rd party developers can hook in via a code event listener.
This would allow 3rd party developers to "unflag" permissions as "Member only" in case their code changes behaviour.

 

[frm]

The 2.3.4 version doesn't really fix the "bug" as it's more of a cosmetic fix, still relying on us to do trial and error to determine which ones we can and can't use, so I am upping this suggestion.

The only suggestion to this suggestion would be to change the phrasing and action to "Available for unregistered users" checkbox so that it's not missed/overlooked, essentially reversing it where if left unchecked it applies to members and when checked it applies to guests. I believe this would make it easier for developers to not have to double-check to confirm whether the box is checked as it would likely not have to be checked in most circumstances.

Fixed Post in thread 'Guests can't attach files'

Oct 30, 2024

@Jeremy P
I can appreciate the note

Note that these permissions apply to both guests and unconfirmed members, and that guests may be prevented from taking certain actions regardless of the permissions set here.

But there is still a UX issue here in that we don't know which ones these apply to. There should be a (?) tooltip next to permissions that they don't apply to, and a way for third-party developers to set a flag on their custom permissions that they don't apply to.

Otherwise, we're still going in blindly with trial and error to determine which ones apply and which...

• frm