SUMMARY *** digiKam 8.3 treats files as if they were read-only. digiKam 8.2 writes the information to the files, but digiKam 8.3 does not. digiKam 8.3 always creates a sidecar file. If you add information and press the Apply button in digiKam 8.3, then add plus additional the information and press the Apply button again, the entered information will be deleted from the input fields. Here is a short video about the problem: https://youtu.be/PIUuEWKpjGI -- The correct behavior of digiKam 8.2 in the first half of the video -- Incorrect behavior of digiKam 8.3 in the second half of the video -- The environment is the same in both cases. Environment: -- Linux Server -- Database: MySql -- Sample File(s) right(s): -rw-rw-rw -- digiKam version: digiKam-8.3.0-20240103T112058-Win64.exe (Qt6) Settings: Metadata -- Write to sidecar files -- Write to XMP sidecar for read-only item only SOFTWARE/OS VERSIONS Windows: Windows 10
Tested in the digiKam-8.3.0-Qt5-20240103T113356-Win64.exe too. The Qt5 version is works well.
The cause is probably a current test in digiKam-8.3.0 as to whether we can work with Exiv2 in UTF-8 file names. However, as it turns out, it doesn't work. I see that you have non ascii characters in your path. Maik
Git commit 5090ebbf6135ab63e9140f1b339cee61e3d5e836 by Maik Qualmann. Committed on 03/01/2024 at 22:21. Pushed by mqualmann into branch 'master'. Revert "try with UTF-8 Exiv2 file paths under MSVC build" FIXED-IN: 8.3.0 M +1 -1 core/libs/metadataengine/engine/metaengine_comments.cpp M +1 -1 core/libs/metadataengine/engine/metaengine_exif.cpp M +2 -2 core/libs/metadataengine/engine/metaengine_fileio.cpp M +1 -1 core/libs/metadataengine/engine/metaengine_iptc.cpp M +1 -1 core/libs/metadataengine/engine/metaengine_p.cpp M +1 -1 core/libs/metadataengine/engine/metaengine_previews.cpp M +1 -1 core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/graphics/digikam/-/commit/5090ebbf6135ab63e9140f1b339cee61e3d5e836