[Digikam-devel] [digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Net Codger]

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

Net Codger <netcodger at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |netcodger at gmail.com

--- Comment #14 from Net Codger <netcodger at gmail.com> ---
Confirming this bug exists in digiKam 4.6 and the issue has remained since 2009
when it was reported in https://bugs.kde.org/show_bug.cgi?id=215486

When a collection is copied to a new system/disk/partition which naturally has
a different UUID, the database is unable to locate the images or thumbnails.

To rsolve the problem, the UUID and path must be adjusted by manually editing
the digikam4.db AlbumRoots Table.

The bug is that, if digiKam will persist with this method of specifying the
path with UUID in digiKam4.db, there should be a way to edit the path,
including the UUID, from within digiKam settings. If such an option is added,
it should be done so that it is easy for the novice user to browse to the
album/collection and have digiKam handle the UUID lookup and digikam4.db edit
behind the scenes.

Copying a collection to a new disk is a standard user operation for moving,
upgrading, restoring from backups. These operations should not break digiKam to
the point where it cannot be fixed from within the application.

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