-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Not taking into account the .noimage flag #75
Comments
Exact, I could reproduce that one too. |
Ah right! :) |
Sure. |
There's precedent for looking for two files:
|
This comment has been minimized.
This comment has been minimized.
Yep. I have a music folder with really a lot of sub-folders, many having an Album Cover image. Showing these images in Photos not a way to go. |
Fixes #75 When a folder has a .noimage or .nomedia node. Just don't show the folder in the album overview. Ignore it and do not traverse it. Signed-off-by: Roeland Jago Douma <[email protected]>
Fixes #75 When a folder has a .noimage or .nomedia node. Just don't show the folder in the album overview. Ignore it and do not traverse it. Signed-off-by: Roeland Jago Douma <[email protected]>
My Nextcloud Server version is 18.0.1 and the Photos App version is 1.0.0, the problem still exist. Do I need to upgrade the Photos App? |
@slgray which view are we talking about here? |
Ah, it is not taken into account there though 🤔 |
Got it, thanks. |
I'm running Nextcloud 18.0.1 with Photos 1.0.0, but the bug still occurs. Can somebody help me getting this fixed through an update or so? |
That wouldn't fix it, that would only obscure it. It should still be possible to add a .nomedia file into some subdirectory of the designated "photos" tree, for instance, to block off a thumbnails directory. |
-> #234 |
Any update on this? It is still an issue in Nextcloud 22 |
@steve4835 This is fixed in Nextcloud 24 |
Bug not resolved. I added Please make sure that |
Hi @q2apro |
Folders with the file
.noimage
are still viewable.The text was updated successfully, but these errors were encountered: