Bug 194211 - "do not delete important posts" flag is not being respected
Summary: "do not delete important posts" flag is not being respected
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-26 21:44 UTC by Tomas Pospisek
Modified: 2017-01-07 21:58 UTC (History)
1 user (show)

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


Attachments
akregatorrc (2.40 KB, application/octet-stream)
2010-06-16 00:26 UTC, Tomas Pospisek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Pospisek 2009-05-26 21:44:03 UTC
Version:           1.4.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-11-generic

If I mark a posting as "important" and switch to a different feed, and come back again, that posting is gone.

This sucks a lot, since akregator is deleting _the most important posts_! :-((( !

The flag "do not delete important articles" in the "archive" configuration section is switched on.
*t

(My akregator is all in german, so the text quoted above are actually my 
 translations from german to english - I guess you will be able to guess the 
 precise english texts within akregator)
Comment 1 Frank Osterfeld 2009-07-26 22:13:27 UTC
Cannot reproduce. The important flag is handled here as expected (4.3 though, but there wasn't a fix in that area to my knowledge). Which archive settings do you use? (Expiry, or "No archive" in Advanced page of the Settings).
Comment 2 Tomas Pospisek 2009-07-26 23:13:21 UTC
On Sun, 26 Jul 2009, Frank Osterfeld wrote:

> Cannot reproduce. The important flag is handled here as expected (4.3 though,
> but there wasn't a fix in that area to my knowledge). Which archive settings do
> you use? (Expiry, or "No archive" in Advanced page of the Settings).

In Settings->Configure Akregator->Archive
                                     ->Delete articles older than: (60 days)
                                     ->(x) Do not expire important articles
                                 ->Advanced->(x) Mark selected article as
                                                 read after: (0 sec)

Right-click a feed->Edit Feed->Archive->(x) Use default settings
                              ->Advanced Settings->() Mark articles as read
                                                   when they arrive (not set)
                                                 ->Archive backend: (Metakit)

That's about those archive settings that I could find. Please do ask 
further if there are some settings somewhere that I didn't catch.
*t
Comment 3 Tomas Pospisek 2010-05-22 18:45:12 UTC
Wow, this is _still_ reproducible with 4:4.4.2-0ubuntu5.
Comment 4 Christophe Marin 2010-06-12 14:24:41 UTC
I'm still unable to reproduce with ~4.5beta2.

I tried:
- set 'delete older than 1 day' for a given feed,
- mark a few messages in this feed as important,
- wait 24 hours,

The important messages are still there while the normal ones were deleted.
Comment 5 Tomas Pospisek 2010-06-12 18:44:56 UTC
(In reply to comment #4)
> I'm still unable to reproduce with ~4.5beta2.
> 
> I tried:
> - set 'delete older than 1 day' for a given feed,
> - mark a few messages in this feed as important,
> - wait 24 hours,
> 
> The important messages are still there while the normal ones were deleted.

I don't have to wait to have the "important" messages deleted. I simply have to switch between two different feeds - that's it.

So again: I go to a feed, select a posting/message, mark it as important, I select a different feed, I select the first feed again and voilà, the message that was marked as important is no more there.

I can provide you with all the settings if you want. I can't test V4.5 though, since I'm on 4.4.
*t
Comment 6 Christophe Marin 2010-06-14 10:24:11 UTC
Good idea, please attach your akregatorrc (from ~/.kde/share/config) and your feeds.opml (from ~/.kde/share/apps/akregator/data)
Comment 7 Tomas Pospisek 2010-06-16 00:26:29 UTC
Created attachment 48050 [details]
akregatorrc
Comment 8 Tomas Pospisek 2010-06-16 00:29:03 UTC
I'm sending you my feeds with private mail - I don't want them to be published here.
Comment 9 Denis Kurz 2016-09-24 19:42:26 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 10 Denis Kurz 2017-01-07 21:58:10 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.