| Summary: | Reread Metadata From File doesn't cleanup Tags | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | spiesant <spiesant> |
| Component: | Tags-Keywords | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.0.0 | |
| Sentry Crash Report: | |||
|
Description
spiesant
2022-12-18 04:31:43 UTC
No, the tag definitely disappears after reading in the metadata again. If writing is activated e.g. for tags, the corresponding database entries are previously cleaned in digiKam-8.0.0. Since I know that you are using 2 digiKam instances, I suspect that you have not enabled tag writing in the reading digiKam instance. digiKam-8.0.0 only cleans up the database when reading again if writing the relevant metadata is also activated. Maik (In reply to Maik Qualmann from comment #1) > No, the tag definitely disappears after reading in the metadata again. If > writing is activated e.g. for tags, the corresponding database entries are > previously cleaned in digiKam-8.0.0. Since I know that you are using 2 > digiKam instances, I suspect that you have not enabled tag writing in the > reading digiKam instance. > digiKam-8.0.0 only cleans up the database when reading again if writing the > relevant metadata is also activated. > > Maik This test was done in just one instance, so that's not the issue - but hmm, you're right, it seems like I now am *not* able to repro the issue with just the above steps. When I observed the behavior, I had done a number of tag adds, and then reverted one file from backup, but couldn't seem to get digiKam to reflect that that the tags had been removed. It was admittedly a longer series of steps that led to that though, which I simplifed to the above. Was sure I'd reproduced it just like that, but in this moment I no longer can, so perhaps it was one of the prior actions that ultimately led to the situation. Anyway, since it seems my steps aren't the proper repro, will close this now. Can always re-report in the event that I see it again & can provide better repro steps. Thanks for the quick replies! :) |