Bug 251768 - digikam custom file renaming options are ignored when importing from camera
Summary: digikam custom file renaming options are ignored when importing from camera
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-Import (show other bugs)
Version: 1.4.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-19 23:46 UTC by Tomek
Modified: 2022-02-01 06:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.2.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tomek 2010-09-19 23:46:12 UTC 
Version:           1.4.0 (using KDE 4.5.1) 
OS:                Linux

custom filename format is ignored when importing files from camera (Canano Powershot A470). Entering some custom expression like:
[date:"yyyy_MM_dd_hhmmss"].[ext]
or
[date:ISO].[ext]
ends up in garbage file names (see below).

Reproducible: Always


Actual Results:  
files with names like -1.JPG,, -2.JPG, -3.JPG or IMG_5145.JPG etc.etc.

Expected Results:  
files with names like 2010_09_05_201122.JPG 

It worked fine for 1.3.0
Comment 1 caulier.gilles 2010-09-21 10:31:53 UTC 

*** This bug has been marked as a duplicate of bug 251899 ***
Comment 2 J. D. Cook 2010-09-22 02:36:58 UTC 
KDE: 4.4.4
Qt: 4.6.3
nVidia Driver: 195.36.31 (9800GT+)
Xorg: 1.8.0
openSuSe: 11.3
kernel: 2.6.34.7-0.2-desktop
Comment 3 caulier.gilles 2020-09-12 10:51:30 UTC 
Fixed with #251899