Guest app (v 4.7.4) seems not to submit shares privileges correctly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 61
- Forks
- 34
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 22
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Hi all,
I've been struggeling a lot with the guest app the last couple of days. Today I have seen and installed the update from v 4.7.2 to v 4.7.4. The guest is created successfully and now the guest receives an invitation email and an email whenever a share is set up. I'm very happy so far.
However maybe the file permissions are not being transferred correctly. So far, I have only encountered this problem with a docx-file. Though in the share editing is allowed, for the guest the file doesn't open and clicking on the file in nc-web-ui, the url of the page (collabora online editor) says <nextcloud-domain>/apps/files/files/204?dir=/&editing=false&openfile=true. Can anyone reproduce the behaviour? Have I overseen something?
Steps to reproduce
As user to share something
- Create share by inviting a guest
- Check that share permissions are set to enable editing
- Confirm share -> share is created successfully
As guest
- Login
- Goto shared files
- Click on shared .docx-document
- Window shows spinning wheel stating "Loading filename.docx..."
Expected behaviour
I'd expect the file to open for editing and collaborating
Actual behaviour
File doesn't open for editing, wheel spins forever
Server configuration
Nextcloud version: Hub 26 Winter (33.0.3) / AIO instance v13.0.4
Webserver/PHP as per AIO container
Browser
Browser name: Tested in Firefox 151.0.1 (64-Bit) and Edge 148.0.3967.70 (Offizielles Build) (64-Bit)
Operating system: Windows 11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the guest-app share flow with a shared .docx file, using the listed steps and checking the share's editing permission. Compare the guest's behavior with the expected ability to open and edit the document; done means the file opens instead of showing an endless loading wheel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100