Bug 112025

Summary: digikam overwrites albums previously exported to HTML
Product: [Applications] digikam Reporter: Volker Kuhlmann <bugz57>
Component: Plugin-Generic-HTMLGalleryAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 0.1.0
Sentry Crash Report:

Description Volker Kuhlmann 2005-09-04 12:26:58 UTC 
Version:           0.7.4 (using KDE 3.4.2 Level "b" , SUSE 10.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-3-default

Exporting an album as HTML for the first time is fine, with default settings of "export to ~/Documents/" it goes to ~/Documents/KIPIHTMLExport/albumname/

When wanting to export another album (say "album2") as HTML, there's no reason to change the default export target directory. However, digikam complains "folder ~/Documents/KIPIHTMLExport/ already exists". It should be complainig only if folder ~/Documents/KIPIHTMLExport/"album2" already exists. When cancelling the popup, digikam does nothing. When "ok"ing, digikam DELETES ALL PREVIOUSLY EXPORTED ALBUMS under ~/Documents/KIPIHTMLExport/. Arrgh.
Comment 1 Tom Albers 2005-12-28 19:28:48 UTC 
There can be more albums and thus it is required that the KIPIHTMLExport folder is completely empty. Due to the not-so-optimal code this plugin is written in, it is currently difficult to resolve.
Comment 2 Wennael Lemonnier 2006-01-24 12:14:20 UTC 
Hi, there is another bug report that ask for an incremental export of gallery HTML, I think it  is better to wor in this (95116 incremental local export or other easy web publishing method) than yours, because is better to have an incremental export...
Comment 3 Angelo Naselli 2006-04-19 19:41:08 UTC 
fixed in new plugin