Bug 102113

Summary:	ArchiveMode preference is broken
Product:	[Applications] akregator	Reporter:	Adrien Beau <abe.kde.bugs>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Adrien Beau 2005-03-21 18:34:57 UTC

Version:           1.0.1 (using KDE KDE 3.3.2)
Installed from:    Slackware Packages
Compiler:          gcc (GCC) 3.3.4 Stock Slackware 10.1 compiler
OS:                Linux

I use Slackware 10.1 and KDE 3.3.2. I just compiled and installed Akregator 1.0.1.

The wrong ArchiveMode preference value is stored in the configuration file. This results for example in the articles being deleted from the hard drive when the user asked to keep them. Note that it seems that the deletion only occurs after feed configuration has changed (in my case, after enabling custom update interval for various feeds).

Here are the four possible ArchiveMode settings, the text displayed in the dialog box, and what is written in the configuration file. I use Akregator on a French desktop, so the preference values are written in French, with original English string in parentheses.

Conserver tous les articles (Keep all articles)
[Archive]
Max Article Age=30
Max Article Number=990

Limiter la taille de l'archivage de flux à : (Limit feed archive size to:)
[Archive]
ArchiveMode=limitArticleAge
Max Article Age=30
Max Article Number=990

Supprimer les articles plus anciens que : (Delete articles older than: )
[Archive]
ArchiveMode=disableArchiving
Max Article Age=30
Max Article Number=990

Désactiver l'archivage (Disable archiving)
[Archive]
ArchiveMode=limitArticleNumber
Max Article Age=30
Max Article Number=990

So, if the user wants to keep articles by age, they are removed from the hard drive, and so on.

Comment 1 Teemu Rytilahti 2005-03-21 18:47:05 UTC


*** This bug has been marked as a duplicate of 101907 ***

Comment 2 Adrien Beau 2005-03-21 19:00:09 UTC

Glad too see this has already been fixed. Too bad the other bug seemed to have nothing to do with mine; it would have spared me the time to research and write down this report.

Comment 3 Frank Osterfeld 2005-03-21 19:12:20 UTC

Thanks for reporting anyway, this is an evil one and it's better reported twice ;-)
It was caused by a last minute commit by someone who couldn't know about the problem (see 101907), and my fault was that I wasn't alerted...
I hope not too many users break their archives using "delete articles older than" :-(

Comment 4 Adrien Beau 2005-03-22 09:09:01 UTC

Well, maybe a news item could be posted on the Akregator website to warn users about the issue, and maybe even a 1.0.2 release be made.