Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of the "__anonymous" group for projects/(layers) groups/layers visibility #4233

Open
1 task
gioman opened this issue Feb 23, 2024 · 3 comments
Open
1 task

Comments

@gioman
Copy link
Contributor

gioman commented Feb 23, 2024

What is the question? (in English)

I was under the assumption that the "__anonymous" group was a (special) group that contained everyone visiting LWC while not logged.

But that do not seems to be the case as if I specify "__anonymous" for a "group visibility" property, the project/layer/etc is not visible also for not logged users, almost as if "__anonymous" is considered as a real group.

The difference between leaving "group visibility" empty and using the "anonymous" group is clear, and is between showing something always (user logged or not) and showing something when a user visits LWC while not logged.

Did I get it wrong? Or is not working as expected?

Versions, safeguards, check summary etc

LMWC 3.6.10
QGIS Desktop/Server 3.28.15
LM plugin 4.2.2

Check Lizmap plugin

  • I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 22.04

Browsers

Firefox, Chrome

Browsers version

Latest updates

Relevant log output

No response

@gioman
Copy link
Contributor Author

gioman commented Feb 23, 2024

I understand now (because I really never had a similar use case before) that the logic is the same used when choosing roles/groups in LWC repositories permissions: "anonymous" applies to everyone, logged or not so not only to not logged ones (which is a bit counter-intuitive also with the difference that in LWC backoffice "anonymous" must be checked and in LM plugin the visibility property must be left blank, which is a bit consistent I guess).

Anyway I think there are use cases where it would be desirable to have "anonymous" really apply to only users that are not logged.

@Gustry
Copy link
Member

Gustry commented Jun 19, 2024

Anyway I think there are use cases where it would be desirable to have "anonymous" really apply to only users that are not logged.

It's technically possible if you put a single comma I think. But this is very hacky. A proper way should added indeed.

@gioman
Copy link
Contributor Author

gioman commented Jun 19, 2024

It's technically possible if you put a single comma I think. But this is very hacky. A proper way should added indeed.

@Gustry thanks, I will give it a try. The label for this ticket should be changed I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants