Network Shares inaccessible (to digikam) after transition to digikam v5.1 (schema v.8)
Gilles Caulier
caulier.gilles at gmail.com
Tue Sep 27 06:26:27 BST 2016
The encoding path to root collection is badly encoded. In fact this is due
certainly to port to pure Qt5 implementation, previous one use KUrl instead
Qt5::QUrl.
Note : this is another point to prohibit the KDE API and to always promote
Qt API instead everywhere. This kind of dysfunction are unacceptable for an
application as digiKam. As now the 800.000 lines of code drop 90% of KDE
API, the future will be more stable.
The solution to your problem is to fix the encoding path of root collection
in DB. Look in Setup collection dialog if paths are show properly.
Gilles Caulier
2016-09-27 7:01 GMT+02:00 <digikam-ng.jg at graumannschaft.org>:
> Hello,
>
> After I managed to upgrade on my debian stable/testing system from digikam
> 4.*
> to 5.1 (see an earlier post), I now have a new issue: the path definition
> of my
> network drive stored albums has NOT changed during the database migration,
> however digikam 5.1 is unable to access the images stored on the network -
> when clicking on the thumbnail, the real image is NOT loaded and when
> trying
> to create a new sub-album/directory in the left album pane (where the
> network
> stored albums show up just fine), I get a complaint that "file://<path to
> network share missing here>/<parent of the dir to create>" does not exist.
>
> When looking at the corresponding AlbumRoots table using mysql-workbench, I
> get this: https://ibin.co/2wTxwWM8Pitj.png
>
> What's going wrong and how to fix it?
>
> Sincerely, Joh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20160927/a2befb3a/attachment.html>
More information about the Digikam-users
mailing list