Have you enabled troubleshooting mode?
Describe the bug
When .nogallery marker is added to a directory that already has a folder-based gallery, running the Clean task leaves that gallery in the database.
The marker prevents a new folder-based gallery from being created during Scan, but it has no effect on a gallery that was created before the marker was added.
As a result, .nogallery cannot be used to opt an existing directory out of folder-gallery creation without manually deleting the gallery.
Steps to reproduce
- Enable Create galleries from folders containing images in the Library settings.
- Add a directory containing one or more images to a Stash library.
- Run Scan and confirm that Stash creates a folder-based gallery for that directory.
- Create a lowercase file named
.nogallery inside the same directory.
- Run Clean for the library, or selectively for a path containing that directory.
- Open the Galleries page.
Observed result: the folder-based gallery remains in the database even though its directory now contains .nogallery.
Expected behaviour
Clean should remove the folder-based gallery from the database when its directory contains .nogallery.
There are also details like:
- what to do with images when the gallery is deleted by
.nogallery reason? Probably they should stay, since scanning such folders would still produce images, but would not produce the gallery (questionable logic to begin with, but choosing consistency is simpler)
.forcegallery and .nogallery files in the same folder conflict - resolve the same way scanning does - force has precedence
Screenshots or additional context
not relevant
Stash version
0.31.1
Device details
not relevant
Relevant log output
not relevant
Have you enabled troubleshooting mode?
Describe the bug
When
.nogallerymarker is added to a directory that already has a folder-based gallery, running the Clean task leaves that gallery in the database.The marker prevents a new folder-based gallery from being created during Scan, but it has no effect on a gallery that was created before the marker was added.
As a result,
.nogallerycannot be used to opt an existing directory out of folder-gallery creation without manually deleting the gallery.Steps to reproduce
.nogalleryinside the same directory.Observed result: the folder-based gallery remains in the database even though its directory now contains
.nogallery.Expected behaviour
Clean should remove the folder-based gallery from the database when its directory contains
.nogallery.There are also details like:
.nogalleryreason? Probably they should stay, since scanning such folders would still produce images, but would not produce the gallery (questionable logic to begin with, but choosing consistency is simpler).forcegalleryand.nogalleryfiles in the same folder conflict - resolve the same way scanning does - force has precedenceScreenshots or additional context
not relevant
Stash version
0.31.1
Device details
not relevant
Relevant log output
not relevant