WeblateOrg / WeblateOrg/weblate
Translations coordinator cannot add new language
- Dominant language
- Python
- Stars
- 6.1k
- Forks
- 1.4k
- Avg merge
- 9h 53m
- Merged PRs (30d)
- 395
Description
### Describe the issue
A user with the Translations coordinator role cannot add a new language to a component group.
### I already tried
- [x] I've read and searched [the documentation](https://docs.weblate.org/).
- [x] I've searched for similar filed issues in this repository.
### Steps to reproduce the behavior
1. Make sure to have a Team which exclusively has the 'Translations coordinator' role
2. Make a user part of this Team
3. As that user, go to Project > Language > Component group
OR
As that user, go to Project > Component group > Languages
### Expected behavior
On the component group page with the list of components, the list of missing components are expected to show up as not-yet-existing, and they can be clicked to be added:
On the languages list, the plus button to add a new language is expected to show.
### Screenshots
The user in question is part of the following teams:
Each of the teams map to their equivalent role:
The view of the user: Project > Language > Component group
### Exception traceback
```pytb
```
### How do you run Weblate?
weblate.org service
### Weblate version
?
### Weblate deploy checks
```shell
```
### Additional context
Our translations coordinator notes that adding the component (group) in a language was possible before. As far as we can recall, we have not changed the user's permissions, so we suspect it's a bug.
CC: @delthia
Contributor guide
Research direction
Start by reproducing the issue with a team limited to the Translations coordinator role, using the two Component group language entry points described in the report. Trace the permission checks controlling missing-component links and the add-language plus button. Done means the coordinator can add a language or component group from both relevant views without granting broader permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- authorization, backend, localization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100