Repository navigation
[Bug]: url share not working #40104
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
One way to share a file to a colleague is to just copy over the URL in your browser location bar to a specific file. This works, seemingly, for some people - but it doesn't for me 😢
Steps to reproduce
- (colleague) copy URL to a file
- (me) paste in top or click link
- it starts loaded, then I get redirected to https://cloud.nextcloud.com/apps/files/files?dir=/&fileid=350
Expected behavior
Load the url! It works if I copy a URL myself...
Installation method
None
Nextcloud Server version
27
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Activity
jospoortvliet commentedon Sep 3, 2023
Issue seems to be that the 'mount point' for me is different than for the other user - in this case, by a completely trivial capital character (
/Marketing/instead of/marketing/). As the file id is there in the URL, an user would expect the file to be found anyway - which works fine when simply a 'internal share' is used (https://server/f/fileID) - in other words, dir seems to take precedence over file ID.Fascinatingly, loading the page works initially - it seems to be loading the right folder, then suddenly going back to root and redirecting to a different file (ID 350 for me, other colleagues have seen the redirect happen to random other file ID's).
What I would expect to happen is a check if the location given in
dircan be loaded, failing that, simply using the fileID to locate the file and folder. Perhaps more robust would be to simply ignoredirand go to the file ID but I suppose files with the same ID can be in multiple locations...joshtrichards commentedon Sep 19, 2023
Same as #32177?