-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
Media in shared folders (share link) does not load #551
Comments
Have you enabled federated sharing on your server? |
No, federated sharing is disabled. Is that now a requirement for stuff like this? |
Or maybe a list of all enabled apps:
On the sharing settings page everything but search global or public address book for users is unchecked. |
yep! Please enable it again :) |
Describe the bug
The issue is that media inside a folder shared via a share link cannot be loaded. For now I know that movies (e.g. mp4, mov) and images (.png and .jpg) are affected.
Existing bug entries for the files_videoplayer app (e.g. nextcloud/files_videoplayer#130 or nextcloud/files_videoplayer#159) seem do hint in that direction but they do not describe our problem accurately.
The very same images or videos can be played or displayed when accessed normally through your files library so this does not seem to be a general file format issue.
Curiously enough said media can be loaded when shared directly via share links instead from inside a folder.
We operate a productive and a test environment of Nextcloud, both are at version 18.0.6 and this is reproducible on both instances.
Nextcloud does not seem log anything. The only hint I can give is the return value the browsers give: 401
To Reproduce
4.1 Everything except images and videos can be loaded and displayed
4.2 The loading screen is shown instead of showing the image or video
Expected behavior
Images and Videos should be loaded and shown just fine.
Screenshots
Well, the loading screen...
Desktop (please complete the following information):
Browser log
The text was updated successfully, but these errors were encountered: