Closed th0rgall closed 3 weeks ago
Thank you for the detailed analysis! I already have a suspicion what is broken and will try to investigate soon.
Any update on this issue? I have had to disable the app and miss it.
Still no fix ? This is a very annoying problem.
Hey @astro-1999, @NeilSauv, and others passing by here, if this issue affects you too, consider giving the opening post a 👍 This is more likely to help with prioritization.
Context
I have an WebDAV External Storage with pictures, say
ExternalPhotos
. The root folder of this storage has a.nomedia
file. The folders in the storage are organized byYYYY/MM
.I added a folder 01 to 2021, and then ran
./occ preview:generate-all
.This lead to the expected behavior, the 2021/01 folder was skipped, because the root
ExternalPhotos
was skipped. Log file entry:Problem
Afterwards, I ran
./occ preview:pre-generate
. Now it unexpectedly started indexing 2021/01 on the external storage.I presume that this is due to the difference in the behavior commands:
generate-all
does a full top-down scan of the Nextcloud instance directory tree, and therefore notices the.nomedia
inExternalStorage
pre-generate
does not attempt a full scan, but only looks at the log of modified/added directories since the last time it ran (there are some hints about this in the README/info about this app). SinceExternalStorage/2021/01
was added, it would only check forExternalStorage/2021/01/.nomedia
, and not forExternalStorage/.nomedia
or.nomedia
files in any other ancestral folder.Workaround
This suspicion was further confirmed when I added .nomedia files to
2021
and2021/01
. Now,pre-generate
didn't attempt to generate the previews anymore.Solution?
Is my suspecion about this (for me) unexpected behavior correct?
If so, I think it would be nice if
pre-generate
scanned all ancestor folders of modified folders for.nomedia
files, and not just the folder itself. That would make it behave as I expect.