Bug 372047

Summary:	Switch from DK4 to DK5 fails: collection path contains %2F instead of /
Product:	[Applications] digikam	Reporter:	Frank Steinmetzger <dev+kde>
Component:	Setup-Database	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	apero70, caulier.gilles, marty
Priority:	NOR
Version:	5.2.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:	7.5.0
Sentry Crash Report:

Description Frank Steinmetzger 2016-11-03 22:32:57 UTC

I’m a user of Digikam 4.14 and trying out a freshly built 5.2.0 on my Gentoo system with Plasma 5.8.3, frameworks 5.26.0.

After going through the conversion wizard, I see the root entry of the collection I am trying to migrate in the album tree, but after a short moment it vanishes and I see a progress popup at 100 %.

The tag tree is still there. The timeline also shows how many images I have for a given month. But this one is cleared once I closed and reopened Digikam.

I found out that in Digikam’s Settings→Collections I see the collection that I tried to migrate, but its path is written as "%2Fhome%2Ffrank%2Fbilder". So I delete that, add a new collection with the proper path, click OK and then the collection is correctly imported. Quickly glancing over it, all tags and so on seem to be there. After a while of processing, the timeline is also populated again.

Comment 1 caulier.gilles 2016-11-03 22:38:07 UTC

Must be fixed with next digiKam 5.3.0.

Please test and report with preview of 5.3.0 AppImage bundle for Linux :

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

Comment 2 Frank Steinmetzger 2016-11-15 20:58:28 UTC

5.3.0 reached my package manager, so I could easily install it. I have several collection databases which I manage independently from one another. It appears to me that migration is only performed on the database that was last opened in Digikam 4, because that is what the migration wizard can find. The migration worked successfully and I can browse my collection.

However, Any other database that is opened afterwards is not migrated and keeps the '%2F'. I checked my digikam4.db files, and indeed the identifier column in the AlbumRoots table of the first database was adjusted ("volumeid:?path=" now uses / instead of %2F). But in the second database file it still said %2F.

Comment 3 Arnaud 2017-04-28 05:02:02 UTC

Hello,
is there a way to modify the path in DK 5.2.0, I get the same bug, since I upgrade Opensuse from 42.1 to 42.2. May I delete the collection with the %2 and add a same new one with / ? 
Does the DB will recognise the new path or I will lost some tags, ...
Thank you,
Arnaud

Comment 4 Maik Qualmann 2017-05-01 19:06:10 UTC

*** Bug 379415 has been marked as a duplicate of this bug. ***

Comment 5 Marty 2017-05-01 19:40:56 UTC

Folks i hit this upgrading from 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 sqllite database directly replacing the ascii %2F with / and when i restarted everything was fine again.

Comment 6 Arnaud 2017-05-02 21:29:57 UTC

(In reply to Marty from comment #5)
> Folks i hit this upgrading from 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 sqllite database directly replacing the ascii %2F with / and
> when i restarted everything was fine again.

Just did it, works like a charm ! Thank you very much.

Comment 7 caulier.gilles 2020-08-02 13:03:20 UTC

digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier