nextcloud / nextcloud/previewgenerator
Federated shares seem to be ignored
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 520
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
My partner has their own Nextcloud instance on their own server, and they're sharing their photos with me using the federated shares system that Nextcloud provides.
Using the generate-all command, previews for files shared in this manner are generated just fine. However, when a file in a share is changed, or an entirely new share is added, no new previews seem to be generated using the pre-generate command.
After some investigation, it seems that no entry about the newly added/changed file is even added into the oc_preview_generation table, which explains why no previews are being generated. Though I can't be sure, since I have little experience with the Nextcloud API, it seems like the NodeWrittenEvent that the preview generator listens to isn't being fired for files in federated shares.
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 tracing how the pre-generate command handles changes and new files compared with generate-all, then investigate whether NodeWrittenEvent is fired for federated shares. Check the oc_preview_generation table while reproducing the issue; done means changed or newly shared files are queued and previews are generated by pre-generate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100