When making an album private, user "guest" is listed like any other user to be granted access. While it's a feature used by a very few administrators, it is far more often used by mistake. I would prefer to have "guest" removed. The problem is that we can't disable it in case it was used on purpose. So I propose to have a configuration setting like $conf['album_permissions_list_guest'] to false by default, unless it was used in the past.
When making an album private, user "guest" is listed like any other user to be granted access. While it's a feature used by a very few administrators, it is far more often used by mistake. I would prefer to have "guest" removed. The problem is that we can't disable it in case it was used on purpose. So I propose to have a configuration setting like `$conf['album_permissions_list_guest']` to `false` by default, unless it was used in the past.
<img width="680" alt="Screenshot 2023-05-16 at 12 23 10" src="https://github.com/Piwigo/Piwigo/assets/9326959/0bd8830e-d594-4484-8b47-0bb9d26466d1">
<!-- github-sync-id:1711721753 -->
Actually it's more a "manage permissions for guest" settings which includes:
listing "guest" in the list of users for album permission
"guest" user edit popin : "permissions" button, associate to groups, set the privacy level
Actually it's more a "manage permissions for guest" settings which includes:
- listing "guest" in the list of users for album permission
- "guest" user edit popin : "permissions" button, associate to groups, set the privacy level
<!-- github-comment-id:1549485386 -->
If manage permissions for guest is set to false, should we allow "guest" to be added to a group?
If an administrator switches this setting to false and that "guest" had permissions or was in a group (with permissions), should Piwigo remove permissions and remove "guest" from its groups? (I would say "yes")
A few thoughts about this topic...
If `manage permissions for guest` is set to `false`, should we allow "guest" to be added to a group?
If an administrator switches this setting to `false` and that "guest" had permissions or was in a group (with permissions), should Piwigo remove permissions and remove "guest" from its groups? (I would say "yes")
<!-- github-comment-id:1748938426 -->
If manage permissions for guest is set to false, should we allow "guest" to be added to a group?
it should still be able to, since plugins may use "technical" groups in order to set permissions, options etc. to several users at once.
If an administrator switches this setting to false and that "guest" had permissions or was in a group (with permissions), should Piwigo remove permissions and remove "guest" from its groups? (I would say "yes")
That's tricky technically but yes: if someone use the Guest for permissions then change its mind, he probably expects Piwigo to remove Guest from the permission list of all albums
Hi Pierrick!
> If `manage permissions for guest` is set to `false`, should we allow "guest" to be added to a group?
it should still be able to, since plugins may use "technical" groups in order to set permissions, options etc. to several users at once.
> If an administrator switches this setting to `false` and that "guest" had permissions or was in a group (with permissions), should Piwigo remove permissions and remove "guest" from its groups? (I would say "yes")
That's tricky technically but yes: if someone use the Guest for permissions then change its mind, he probably expects Piwigo to remove Guest from the permission list of all albums
<!-- github-comment-id:1748978183 -->
If manage permissions for guest is set to false, should we allow "guest" to be added to a group?
it should still be able to, since plugins may use "technical" groups in order to set permissions, options etc. to several users at once.
Do you have a specific example in mind where it would be useful to have "guest" permitted to do something thanks to belonging to a group?
I agree that groups are not only for album permissions, but I would like to have some good arguments to keep "guest" in groups.
I also don't think it would be a good idea to have "guest" in groups but not taking it into account for permissions.
> > If `manage permissions for guest` is set to `false`, should we allow "guest" to be added to a group?
>
> it should still be able to, since plugins may use "technical" groups in order to set permissions, options etc. to several users at once.
Do you have a specific example in mind where it would be useful to have "guest" permitted to do something thanks to belonging to a group?
I agree that groups are not only for album permissions, but I would like to have some good arguments to keep "guest" in groups.
I also don't think it would be a good idea to have "guest" in groups but not taking it into account for permissions.
<!-- github-comment-id:1749021050 -->
Today a user reported a "bug": 2 of her private albums were visible to anonymous visitors. Of course, it was because the 2 private albums had been authorized to guest.
Even with the manage permissions for guest setting could make things confused. We should also have a specific warning on the permissions page for guest:
Warning, you're editing permissions for anonymous visitors. Do it knowingly.
Today a user reported a "bug": 2 of her private albums were visible to anonymous visitors. Of course, it was because the 2 private albums had been authorized to `guest`.
Even with the `manage permissions for guest` setting could make things confused. We should also have a specific warning on the permissions page for guest:
> Warning, you're editing permissions for anonymous visitors. Do it knowingly.
<!-- github-comment-id:2589650932 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When making an album private, user "guest" is listed like any other user to be granted access. While it's a feature used by a very few administrators, it is far more often used by mistake. I would prefer to have "guest" removed. The problem is that we can't disable it in case it was used on purpose. So I propose to have a configuration setting like
$conf['album_permissions_list_guest']tofalseby default, unless it was used in the past.Actually it's more a "manage permissions for guest" settings which includes:
A few thoughts about this topic...
If
manage permissions for guestis set tofalse, should we allow "guest" to be added to a group?If an administrator switches this setting to
falseand that "guest" had permissions or was in a group (with permissions), should Piwigo remove permissions and remove "guest" from its groups? (I would say "yes")Hi Pierrick!
it should still be able to, since plugins may use "technical" groups in order to set permissions, options etc. to several users at once.
That's tricky technically but yes: if someone use the Guest for permissions then change its mind, he probably expects Piwigo to remove Guest from the permission list of all albums
Do you have a specific example in mind where it would be useful to have "guest" permitted to do something thanks to belonging to a group?
I agree that groups are not only for album permissions, but I would like to have some good arguments to keep "guest" in groups.
I also don't think it would be a good idea to have "guest" in groups but not taking it into account for permissions.
You know it's been a while since I'm not into it.
I don't have specific examples indeed.
Today a user reported a "bug": 2 of her private albums were visible to anonymous visitors. Of course, it was because the 2 private albums had been authorized to
guest.Even with the
manage permissions for guestsetting could make things confused. We should also have a specific warning on the permissions page for guest: