| Summary: | Regression : when batch renaming file (F2), only the first modifier is taken into account | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Vincent Danjean <vdanjean.ml> |
| Component: | AdvancedRename-engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.7.0 | |
| Sentry Crash Report: | |||
The problem is already fixed in digiKam-7.7.0. Maik This was the commit: https://invent.kde.org/graphics/digikam/-/commit/6330e608f9e477253a3982a4e88abf1c901fe0c2 Maik Thanks. I will wait for an update of the Debian package. |
STEPS TO REPRODUCE 1. Select several files 2. Type 'F2' 3. Use a rename expression such as: [date:"yyyy-MM-dd_HH-mm-ss"]_[file]{lower}{range:16,}.[ext]{lower} OBSERVED RESULT Only the first modifier (the first {lower} here) is now taken into account {range:16,} and the second {lower} modifier are ignored (and they are with a red background in the expression) Removing the first modifier (the first {lower}) makes the next one working ({range:16,} here) The first (and so working) modifier do not have the red background EXPECTED RESULT All modifiers should be taken into account. This is a regression. It has been working for several years (at least since 2010) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable / kde 5.90.0 Qt Version: 5.15.2