Album view doesn't show the album being moved in the new location. It appears only after digiKam is restarted. Reproducible: Always Steps to Reproduce: 1. Create a new empty album. 2.Try to move an existing album (with several images) in this new album. Actual Results: Album moved isn't visible in the new location unless restarted. Expected Results: Album moved should be visible in the new location after action is completed.
Issue is reproducible for both MySQL and SQLite.
reproducible here too... Gilles Caulier
Albums are even visible after deletion in UI. If tried to delete again --> "Album doesn't exist" In this case too, Album view is updated only after restarting.
Both album viewing problems not to reproduce here. Swati, only in the root album or also sub-albums? Maik
Both are reproducible for me in sub-albums.
Swati, can you please upload a console log? From start of digiKam up to delete/move an album. Maik
Created attachment 100742 [details] Console log while moving album First I created a new album "Testing5" under "Test Album". ("Test Album" already had sub albums before like "New Album", "Testing1" ,"Testing2"....) This log is result of moving "New Album" under "Testing5".
Git commit 25a0431a0bf97192cee802444d074f79c8b0f01b by Maik Qualmann. Committed on 25/08/2016 at 10:29. Pushed by mqualmann into branch 'master'. remove suspendCollectionScan() from FileActionMngrDatabaseWorker M +0 -18 libs/fileactionmanager/databaseworkeriface.cpp M +0 -2 libs/fileactionmanager/databaseworkeriface.h http://commits.kde.org/digikam/25a0431a0bf97192cee802444d074f79c8b0f01b
Guys, I'm experiencing something similar here but not only when moving Albums but also when deleting a single picture. It is moved to trash (on the filesystem), it is visible in the Trash tree in the Albums list but the image is still visible in the Album View. If I hit refresh, the thumbnail for that image is gone but replaced with the generic filetype thumbnail. Only if I restart digikam does the Album View get updated correctly ... It's making the program unusable for sorting/selection part of the workflow ! Should this be part of this bug ? or filed under a different one ?
The problem sound like fixed with commit from comment #8. If fact not dysfunction is reproducible here with current implementation Gilles Caulier
Yes, I close now this bug. Maik