-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Search: Ignore deleted albums when using the "unsorted" filter #3051
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
Comments
Signed-off-by: Michael Mayer <michael@photoprism.app>
A preview build is already running, but we'll start another one soon so you can test the fix. |
Updated Release Notes will be available soon as well: |
Wow.. uh.. I'll have to setup to test this real soon. I hope I can move as quickly as you are. |
I just setup a test photoprism (pulling from
I will now figure out how to pull a development preview image.. and re-test the same scenario |
Ah.. pulling Using the same (possibly slightly corrupted) library from the previous comment - but with the preview image Hmm.. interesting - the 'missing' photos from (5) above - have come back into 'Unsorted' view. That is promising - but I'm also a little surprised.. but ok, I haven't looked at any of the code changes Since I have ~300 photos .. I'll just start from
I'm not sure how much more testing you'd like from me on this one - but things seem better for sure. |
Thanks for testing :) |
1. What is not working as documented?
Using the "Unsorted" feature photoprism/library/unsorted we are moving photos into albums.
An album was accidentally created with the wrong name. Since being in an album is just a 'tag' on a photo, it felt safe to delete the album (and yes, we know that albums can be renamed).
The photos were no longer in "Unsorted". In our panic, it also felt like they were missing from "Search" (but we may have been mistaken). They were not in the archive either (but we initially suspected the photos in the album were also deleted)
After hunting around, we located the photos in the Folders photoprism/library/folders
This allowed us to recreate the album and all is well.
This still feels like a bug.
2. How can we reproduce it?
Steps to reproduce the behavior:
3. What behavior do you expect?
When an Album is deleted, assuming those photos only were in a single album, those photos should return to the unsorted view.
4. What could be the cause of your problem?
I'm guessing - but I suspect the Album delete is just removing the Album, and does no clean up of any photos in that album. Thus the photo is still in an Album - but there is no Album to be in.
5. Can you provide us with example files for testing, error logs, or screenshots?
This should be simple to reproduce with the steps in (2)
6. Which software versions do you use?
(a) PhotoPrism Architecture & Build Number: AMD64, ARM64, ARMv7,...
AMD64
PhotoPrism® CE Build 221118-e58fee0fb
(b) Database Type & Version: MariaDB, MySQL, SQLite,...
MariaDB - mariadb:10.5
from: https://hub.docker.com/_/mariadb
(c) Operating System Types & Versions: Linux, Windows, Android,...
Firefox (latest) on M1 OSX (Mac Air)
Linux AMD64 hosting docker containers for photoprism
(d) Browser Types & Versions: Firefox, Chrome, Safari on iPhone,...
Firefox (latest)
(e) Ad Blockers, Browser Plugins, and/or Firewall Software?
pi-hole network wide ad blocker
7. On what kind of device is PhotoPrism installed?
(a) Device / Processor Type: Raspberry Pi 4, Intel Core i7-3770, AMD Ryzen 7 3800X,...
Intel Pentium
(b) Physical Memory & Swap Space in GB
16GB with 4GB swap
(c) Storage Type: HDD, SSD, RAID, USB, Network Storage,...
Mix of RAID1 SSDs + snapraid on large mixed spinning disks
(d) Anything else that might be helpful to know?
No. Thank you for your work on this project.
Always provide device, memory, and storage details if you have a backend, performance, import, or indexing issue.
8. Do you use a Reverse Proxy, Firewall, VPN, or CDN?
Yes. Fronted by nginx https://hub.docker.com/r/linuxserver/nginx setup with 'local only' http:// access.
This is not a proxy issue
The text was updated successfully, but these errors were encountered: