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.

Sign up for GitHub

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

Jump to bottom

Button "Lock" does not change to "Unlock" for locked components #4786

Closed
ilocit opened this issue Oct 30, 2020 · 8 comments
Closed

Button "Lock" does not change to "Unlock" for locked components #4786

ilocit opened this issue Oct 30, 2020 · 8 comments
Labels
question This is more a question for the support than an issue.

Comments

@ilocit
Copy link
Contributor

ilocit commented Oct 30, 2020

Describe the bug

I think in previous versions, the button Lock in Repo Mgmnt changed to Unlock when a component was locked.

To Reproduce the bug

Lock component in "Repo"

Expected behavior

Button changes from "Lock" to "Unlock"

Screenshots

If applicable, add screenshots to better explain your problem.
image

Server configuration and status

Weblate 4.3.1
@ilocit ilocit closed this as completed Oct 30, 2020
@github-actions
Copy link

The issue you have reported is resolved now. If you don’t feel it’s right, please follow it’s labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@ilocit
Copy link
Contributor Author

ilocit commented Oct 30, 2020

I was in the porject and thus managing all components, whereas only one of the four cmoponents was locked.
User error.
System behavior as before and as it should be!

@ilocit ilocit reopened this Oct 30, 2020
@nijel
Copy link
Member

nijel commented Oct 30, 2020

The "Lock" button is there as long as there is single unlocked component in the project. It will turn into "Unlock" once all of the components are locked.

@nijel nijel added the question This is more a question for the support than an issue. label Oct 30, 2020
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

@ilocit ilocit closed this as completed Oct 30, 2020
@github-actions
Copy link

The issue you have reported is resolved now. If you don’t feel it’s right, please follow it’s labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@ilocit
Copy link
Contributor Author

ilocit commented Oct 30, 2020

I had closed it already. Since it is not an issue.

@ilocit ilocit reopened this Oct 30, 2020
@ilocit ilocit closed this as completed Oct 30, 2020
@github-actions
Copy link

The issue you have reported is resolved now. If you don’t feel it’s right, please follow it’s labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@ilocit
Copy link
Contributor Author

ilocit commented Oct 30, 2020

Sorry for the mixup, and also for re-opening the issue. Not it should be closed and remain closed 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question This is more a question for the support than an issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nijel @ilocit