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

Updating docs to get ROSETTA_LANGUAGE_GROUPS=True working #279

Open
Skrattoune opened this issue Jul 20, 2023 · 2 comments
Open

Updating docs to get ROSETTA_LANGUAGE_GROUPS=True working #279

Skrattoune opened this issue Jul 20, 2023 · 2 comments

Comments

@Skrattoune
Copy link

  • Which version of Django are you using?: 3.2
  • Which version of django-rosetta are you using?: 0.9.9
  • Have you looked trough recent issues and checked this isn't a duplicate? Yes

Hi,

I'm new to Rosetta, and everything seems to be working fine, but I have a need to give a language-specific access to the translators.

While the access for Superuser works fine, and access through the global translators group works ok,
I'm not able to have access for users defined in the translators-sr or translators-fr where I should see the different django.po and djangojs.po corresponding files

I'm in fact always sent back to the login page http://127.0.0.1:8000/accounts/login/?next=/translations/files/project/ showing that I miss specific access to the rosetta page.

@Skrattoune
Copy link
Author

OK, I was testing something else, and realised that if my user is BOTH in the translators-sr and the generic translators group, suddenly my user sees only the languages he has been assigned to.

Therefore, I guess the the help should be modified from:

ROSETTA_LANGUAGE_GROUPS: Set to True to enable language-specific groups, which can be used to give different translators access to different languages. Instead of creating a global translators group, create individual per-language groups, e.g. translators-de, translators-fr, and assign users to these.

to
ROSETTA_LANGUAGE_GROUPS: Set to True to enable language-specific groups, which can be used to give different translators access to different languages. In addition of creating a global translatorsgroup, create individual per-language groups, e.g.translators-de, translators-fr, and assign users to **both** the global translators group and the language-specific groups they need access to.

@Skrattoune Skrattoune changed the title Not able to get ROSETTA_LANGUAGE_GROUPS=True working Updating docs to get ROSETTA_LANGUAGE_GROUPS=True working Jul 22, 2023
@lmroczek
Copy link

lmroczek commented Jan 3, 2025

Thanks, I ran into the same issue. Adding to both the global group and the language specific group results in the expected behavior.

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

No branches or pull requests

2 participants