[digikam] [Bug 379415] New: digikam collection location string format in 5.X different to 4.X

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 379415] New: digikam collection location string format in 5.X different to 4.X

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379415

            Bug ID: 379415
           Summary: digikam collection location string format in 5.X
                    different to 4.X
           Product: digikam
           Version: 5.6.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database-Sqlite
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

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.

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 379415] digikam collection location string format in 5.X different to 4.X

bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379415

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #1 from Maik Qualmann <[hidden email]> ---


*** This bug has been marked as a duplicate of bug 372047 ***

--
You are receiving this mail because:
You are the assignee for the bug.