| Summary: | Copyright and Right Usage information in Settings are not saved in template file | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Luca Marchetti <ximilian> |
| Component: | Setup-Templates | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | anantapalani, caulier.gilles, marcel.wiesweg, talentedchimp-noreply |
| Priority: | NOR | ||
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
|
Description
Luca Marchetti
2009-10-11 16:15:35 UTC
This could have been an issue with the AltLangStrEdit widget. Some bugs were fixed there recently. Testing with current SVN, both fields were stored and loaded nicely. Copyright and Usages not stored in digikam4.db either. Can one of the reporters here still confirm the bug with 1.0-rc1? Otherwise I suggest to close as WORKSFORME. No answers and I can not confirm it anymore, so I'll close it as WORKSFORME. Uhh.. this is still a problem. When editing a template from the 'Information' tab: 1. Change the language/locale for 'Copyright' and 'Right Usage Terms' to anything other than x-default 2. Edit the fields 3. 'Add' or 'Replace' the template 4. At this point, if you browse among the templates, it appears that digiKam remembers your entry. 5. Click 'OK' Either apply choose the template from the drop-down list or edit the template again. You can see that x-default is chosen as the language. Choosing the previously chosen locale results in an empty field. In summary, the 'Copyright' and 'Right Usage Terms' fields are only stored properly if 'x-default' is the chosen locale. Proposed Solutions: 1. If a language/locale should NOT be chosen for these fields (notice that they cannot be chosen from the information tab!!) then the ability to change locale for 'Copyright' and 'Right Usage Terms' should be removed from the template editor. 2. If a language/locale should be chosen for these fields, add the ability to change locale to the 'Information' tab and store the templates correctly to file and database. I should have said that this is on version 2.2.0 in Windows. I should also mention that none of the fields in the 'Information' tab are manually editable, only a template can be chosen. Choosing a template allows you to 'apply' the template to a given photo, but only the database retains this information; NOTHING is written to the file! I also just noticed that there were two 'templates' that said 'To remove' and 'Do not change'. Does this mean that digiKam doesn't support these fields? If so, why is this entire tab even visible? Note that everything in the 'Description' tab is written to the file just fine, so I don't think it is an issue with the build. Luca, This problem still valid using last digiKam 4.2.0 ? Gilles Caulier Lucas, This problem still valid using last digiKam 4.10.0 ? Gilles Caulier New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier Lucas, This problem still valid using last digiKam 5.0.0 ? Gilles Caulier We need feedback with last digiKam AppImage Linux Bundle: https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release ? It available at this url : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier digiKam 5.5.0 is released officially https://download.kde.org/stable/digikam/ ...and new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows. Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier Please update this entry from bugzilla with current 5.8.0 pre-release bundle to see if problem remain. https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ Gilles Caulier 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 No feedback. Closed. |