Bug 132261 - modified articles are not marked as unread
Summary: modified articles are not marked as unread
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.2.3
Platform: unspecified FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2006-08-11 16:22 UTC by robert wilson
Modified: 2018-10-27 02:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robert wilson 2006-08-11 16:22:10 UTC
Version:           1.2.3 (using KDE 3.5.3, compiled sources)
Compiler:          gcc version 3.4.4 [FreeBSD] 20050518
OS:                FreeBSD (amd64) release 6.1-STABLE

modified articles are not marked as read. this makes it very difficult to tell which threads on message boards using kareha (http://wakaba.c3.cx) have new posts.
i know they used to be marked in an earlier version of akregator.
please change it back or (even better) add an option for this in the configuration dialog.
Comment 1 Frank Osterfeld 2006-08-11 21:13:13 UTC
We decided to switch this off as it caused too many complaints about feeds which were reset to new all the time although they weren't considerably changed. See http://bugs.kde.org/show_bug.cgi?id=101907 for discussion.
We won't change that back in 3.5 branch, we could consider to add an option as workaround though.
For KDE4, akregator should distinguish "unread" and "read but updated" as two independent properties and mark them in separate ways.
Comment 2 Adrián Chaves (Gallaecio) 2012-09-17 06:39:43 UTC
“For KDE4, akregator should distinguish "unread" and "read but updated" as two independent properties and mark them in separate ways.”

Is this already the case? Can the issue be closed?
Comment 3 Myriam Schweingruber 2012-09-17 09:48:37 UTC
Setting status correctly.
Comment 4 Andrew Crouthamel 2018-09-23 02:42:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 02:21:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!