We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a pending share is tried to be accepted/declined using webUI, an error is shown. However, the share is accepted even with an error in the UI.
Steps to reproduce the behavior:
Alice
Brian
simple-folder
The share should be accepted/declined without any error in the webUI.
With the decline action, an error is shown in the webUI. And the share is still in pending state until the page is reloaded.
With the accept action, an error is shown in the webUI. However, the share is shown as accepted only after the page reload.
The text was updated successfully, but these errors were encountered:
Related to owncloud/web#4946
Sorry, something went wrong.
re-tested with local server oCIS version 1.11.0 and web 4.1.0 Works correct, @jasson99 please close
Decline action:
Accept action after decline:
No branches or pull requests
Describe the bug
When a pending share is tried to be accepted/declined using webUI, an error is shown. However, the share is accepted even with an error in the UI.
Steps to reproduce
Steps to reproduce the behavior:
Alice
andBrian
Alice
, share a new created foldersimple-folder
with userBrian
Brian
, decline the pending share using the decline action buttonBrian
, accept the pending share using the accept action buttonExpected behavior
The share should be accepted/declined without any error in the webUI.
Actual behavior
With the decline action, an error is shown in the webUI. And the share is still in pending state until the page is reloaded.
With the accept action, an error is shown in the webUI. However, the share is shown as accepted only after the page reload.
The text was updated successfully, but these errors were encountered: