Bug 379415 - digikam collection location string format in 5.X different to 4.X
Summary: digikam collection location string format in 5.X different to 4.X
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Sqlite (show other bugs)
Version: 5.6.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-01 19:03 UTC by Marty
Modified: 2022-01-08 21:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marty 2017-05-01 19:03:02 UTC 
Folks, i upgraded from 4.14 to 5.6 (via appimage)

It complained it could not find the existing network collections, an example was:
networkshareid:?mountpath=%2Fmnt%2Fmunich%2Fphotos

i edited the AlbumRoots table directly converting the ascii %2F to forward slash and then restarted and everything was fine.

Its not really clear to me why it was represented in hex in 4.X

A local collection did not have same issue and forward slashes were represented directly.
Comment 1 Maik Qualmann 2017-05-01 19:06:10 UTC 

*** This bug has been marked as a duplicate of bug 372047 ***
Comment 2 caulier.gilles 2022-01-08 21:54:42 UTC 
Fixed with https://bugs.kde.org/show_bug.cgi?id=372047