-
Notifications
You must be signed in to change notification settings - Fork 115
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
no office file previews #1865
Comments
I could reproduce this but not on the dashboard and rather just in the file list itself. It seems that removing the filesystem/dav type from app info caused that the preview providers are no longer registered when fetching the file list through webdav. @jakobroehrl to ensure you run into the same issue, could you maybe take the file id of a docx file and try to manually access the preview with that in the browser? https://nextcloud.local/index.php/core/preview?fileId=1739472 You can get the file id as the last part when copying the "internal link" in the sharing sidebar of a file. |
Might be a regression from #1728 |
Another finding to be filed in server, but need to check if it is an issue actually:
|
Hi @juliushaertl manual preview in the browser leads to: [] |
Could you maybe on the nextcloud server issue the following request towards the collabora server url
This should list an entry "convert-to" that tells if the conversion api is properly configured on the Collabora server for preview generation. |
|
Not solved with Version 5 and with the latest collabora docker |
Collabora 21.11 upgraded from 6.4 After days debugging i can confirm that the Collabora ooxml document preview are not generated on the files app "All Files" and "Favorites" tabs and in the Folders. But they are perfectly generated in the Dashboard, "Recent" and "Shares" tabs as well as in the "Insert an image" dialog box. |
is this resolved in Nextcloud 25? |
My office document doesn't have a preview any more:
Tested with 4.1.2 and 5beta on NC22 and NC23
Collabora is running on docker on the same server
The text was updated successfully, but these errors were encountered: