Bug 433311 - New or modified root album folders are always placed into local collections (= Type No 1 in table album roots)
Summary: New or modified root album folders are always placed into local collections (...
Status: VERIFIED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Collections (show other bugs)
Version: 7.2.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-20 09:59 UTC by Frank
Modified: 2021-02-21 09:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.2.0


Attachments
Screenshot from SQL Database (42.97 KB, image/jpeg)
2021-02-20 10:07 UTC, Frank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank 2021-02-20 09:59:32 UTC
SUMMARY
It seems this https://bugs.kde.org/show_bug.cgi?id=347937 problem is back.

STEPS TO REPRODUCE
1. Place an album to network share or removable media
2. Click Ok
3. Reenter the dialog

OBSERVED RESULT
All folders are placed under local collection

EXPECTED RESULT
The folders should stay where they were created

SOFTWARE/OS VERSIONS
Windows: 10 (incl. all updates until Feb. 19th)
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.78.ß
Qt Version: 5.15.2

ADDITIONAL INFORMATION
When chanaging the type in the table "AlbumRoots" manually from 1 to 2 or 3 and do not touch it in digikam it stays where it is.
Comment 1 Frank 2021-02-20 10:07:00 UTC
Created attachment 135955 [details]
Screenshot from SQL Database
Comment 2 Maik Qualmann 2021-02-20 10:09:58 UTC
I don't know what you are doing You shouldn't change the database directly. Only when you know what you are doing. You can change the collection type in the digiKam settings in the collection setup via the refresh symbol next to the trash icon.

Maik
Comment 3 Maik Qualmann 2021-02-20 10:20:30 UTC
It is not enough just to change the type. The identifier and specificPath must have the correct content for the respective collection type. For a local collection e.g. a drive UUID etc.

Maik
Comment 4 Frank 2021-02-20 10:29:13 UTC
(In reply to Maik Qualmann from comment #2)
> I don't know what you are doing You shouldn't change the database directly.
> Only when you know what you are doing. You can change the collection type in
> the digiKam settings in the collection setup via the refresh symbol next to
> the trash icon.
> 
> Maik

Yes, that was what I tried. But the system do not care and re-placed it back into local collections always. I tried to find out what ist the problem by looking directly into the database and found the behaviour as described.

For me it looks as if the dialog always writes a No 1 = local drive into the database on clicking the OK button - independend of the input values
Comment 5 Maik Qualmann 2021-02-20 10:44:25 UTC
The problem is the UNC path, I'll fix it. Drives with letters can be changed without problems.

Maik
Comment 6 Maik Qualmann 2021-02-20 12:03:54 UTC
Git commit 7f064a15e4296a5d512ad63a09c9838e3140cbc1 by Maik Qualmann.
Committed on 20/02/2021 at 12:02.
Pushed by mqualmann into branch 'master'.

fix change collection type from UNC path collection

M  +10   -6    core/libs/database/collection/collectionmanager_location.cpp

https://invent.kde.org/graphics/digikam/commit/7f064a15e4296a5d512ad63a09c9838e3140cbc1
Comment 7 Frank 2021-02-21 09:24:54 UTC
Thanks Maik!
I checked the weekly from yesterday: Problem Solved! It works as expected.
Best Regards
Frank