Skip to content
New issue

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

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

Already on GitHub? # to your account

Themes restricted by role #501

Open
smaspons opened this issue Nov 10, 2023 · 3 comments
Open

Themes restricted by role #501

smaspons opened this issue Nov 10, 2023 · 3 comments

Comments

@smaspons
Copy link

Hello!

I noticed that there's a problem with themes restricted by role, a bit of background:

  • I have two themes (A & B), theme A is the default one
  • I have two roles (role_a & role_b)
  • The theme A can only be seen by role_a and the theme B only by role_b.

The problem is that if the user with role_b opens the app it shows a blank map, as if no theme was selected. If I go to switch themes, I only see the theme B, and I can go to the theme and everything works fine.

Thanks!

@manisandro
Copy link
Member

This is a know issue, currently the only proper solution is to ensure the default theme is public. To properly fix it, we'd need the possibility to set a default theme per role.

@claudiadragoste
Copy link

When a user works with a theme that is not the default theme, what I do is saving for that user the shortcut for the theme that would be his default theme; it can be useful for you too (meanwhile there is no possibility to set the default theme per role):

Example:
In case you work with tenants: https://WebAddress/?t=name_tenant/name_theme
If you don't use tenants: https://WebAddress/?t=name_theme

@manisandro
Copy link
Member

There is since the possibility to set per-user default URL params in qwc_config.user_infos. This might also help for this requirement.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants