Closed phil-davis closed 3 years ago
Ideally the thumbnail of a file would be stored only once, in the "file system" of the file owner. Just like the file itself is stored only once, in the "file system" of the file owner.
If the share receiver "user2" is able to write back new content to the file owned by "user1" (even when encryption is happening) then "user2" should be able to also write back new content to the thumbnail owned by "user1" - and actually that seems to be happening because "user1" is seeing the correct updated thumbnail.
Maybe all that is needed is to stop writing a "duplicate" thumbnail in user2's file system?
GitMate.io thinks the contributor most likely able to help you is @PVince81.
Possibly related issues are https://github.com/owncloud/core/issues/19054 (If thumbnail then large preview in sidebar), https://github.com/owncloud/core/issues/997 (possibility preview and edit docx), https://github.com/owncloud/core/issues/16471 (Can not sync edited remote share file), https://github.com/owncloud/core/issues/7020 (Contact photos only in preview when edited on a client), and https://github.com/owncloud/core/issues/14671 (Thumbnail cache gets deleted after upload from smartphone).
Estimate: 0.5-1md
Concept:
Thank you @phil-davis
When approximately can we have this feature?
It is a bug to be fixed. It depends on scheduling of the dev team, which is not my area.
Steps to reproduce
Expected behaviour
The share receiver "user2" should always see a preview-thumbnail that is in sync with the file content.
Actual behaviour
The share receiver "user2" gets "stuck" with the preview-thumbnail that was generated at the time they first received/looked at the file.
Server configuration
10.0.9RC1 plus PR #31853 (which fixes missing hooks for thumbnail generation in 10.0.9RC1)
10.0.8 as symptoms similar to this, but might be a bit different.