-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Glossary term explanation cannot be added or edited #6283
Comments
What are your component settings for "Manage strings" / "Monolingual base language file" / "Edit base file" on the glossary? |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
nijel
added
bug
Something is broken.
and removed
wontfix
Nobody will work on this.
labels
Aug 3, 2021
nijel
added a commit
that referenced
this issue
Aug 3, 2021
This is confusing when it can be edited but not saved. Issue #6283
nijel
added a commit
that referenced
this issue
Aug 3, 2021
nijel
added a commit
that referenced
this issue
Aug 3, 2021
Thank you for your report; the issue you have reported has just been fixed.
|
nijel
added a commit
that referenced
this issue
Feb 27, 2023
When user can edit flags, but can not save translations, the Save button is needed only for glossaries, otherwise the form would do nothing. Followup to #6283
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
I added an abbreviation as glossary term to the source language (English) and tried to add an explanation.
Things I have observed:
The first screenshot shows the state after steps 1..2, the second one tries to further illustrate my observations.
If you "remove write protection" via the drop down, already entered explanations are lost.
Moving forward or back with the navigation buttons obviously loses the explanation
I would have expected the save button to be active or at least to become active after "remove write protection" was selected
I would have expected all edit functions to be disabled (edit fields, "pen" buttons",...) when the entry is write protected. When I can't edit or save an entry it should be clear from the start. Why should I waste my time entering information that can't be saved.
I already tried
Describe the steps you tried to solve the problem yourself.
If you didn’t try already, try to search there what you wrote above.
Server configuration and status
Weblate 4.7.1 on docker
The text was updated successfully, but these errors were encountered: