| Summary: | Writing metadata to an XMP sidecar removes previously-entered metadata already in the XMP file. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | james |
| Component: | Metadata-Sidecar | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.2.0 | |
| Sentry Crash Report: | |||
|
Description
james
2021-03-15 13:27:46 UTC
Noting that choosing "Item > Write Metadata to File" correctly writes all metadata to the XMP sidecar file. Please test with 7.2.0 pre-release AppImage bundle available here : https://files.kde.org/digikam/ Note : backup your database file before to use 7.2.0, just to be safe. Gilles Caulier I re-tested using digiKam-7.2.0-20210312T180628-x86-64.appimage using a completely fresh database (installed under a different user) with a single photo. The issue is still present. Hmm, the cause is clear, you should actually also enable reading of metadata from sidecars. Editing in the sidebar reads the information from the metadata (image and sidecar) into the container and then writes the new metadata into the sidecar. If reading the sidecar is not activated, only the content of the metadata of the image is written back the next time it is written. In digiKam with a database, we would also have to merge the metadata with the database if reading from sidecar disabled. Maik I'm sure we already have a bug report on it. Maik *** This bug has been marked as a duplicate of bug 395914 *** Fixed with 395914 |