You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the guests app is enabled, a guest user is unable to edit and save an office document which has been shared to them. This is due to the default quota for guests being set to 0.
Give guest users permission to use the richdocuments app
Create a guest user OC_PASS=somepassword php occ guests:add --password-from-env --display-name "guest user" <created-by> [email protected]
Create an office document (in my case a spreadsheet) and share it to the newly created guest user
Open a new browser window and login as the guest user (the username is the email set for the user)
Access the document shared to the guest user and make a few edits
Try to save the document and see the error popups
Expected behavior
The expected behavior is that the share owner's quota is used rather than the guest user's quota. It makes sense for the guest quota to default to 0 for blocking file uploading, but for document editing it makes more sense to handle it differently. If you're sharing a document to a guest with editing permissions, you want them to be able to actually edit and save the document.
Describe the bug
When the guests app is enabled, a guest user is unable to edit and save an office document which has been shared to them. This is due to the default quota for guests being set to
0
.To Reproduce
OC_PASS=somepassword php occ guests:add --password-from-env --display-name "guest user" <created-by> [email protected]
Expected behavior
The expected behavior is that the share owner's quota is used rather than the guest user's quota. It makes sense for the guest quota to default to
0
for blocking file uploading, but for document editing it makes more sense to handle it differently. If you're sharing a document to a guest with editing permissions, you want them to be able to actually edit and save the document.Logs
Nextcloud log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: