Thread: [aKregator-devel] [Bug 101907] New: Read articles keep getting marked as unread after feed fetching
Brought to you by:
lippel
From: Jure R. <jl...@ho...> - 2005-03-19 16:43:52
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 Summary: Read articles keep getting marked as unread after feed fetching Product: akregator Version: 1.0 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: akregator-devel lists sourceforge net ReportedBy: jlp holodeck1 com Version: 1.0 (using KDE 3.4.0, Gentoo) Compiler: gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7) OS: Linux (x86_64) release 2.6.11-gentoo-r3 I just installed Akregator on my Gentoo Linux machine. I'm runing KDE 3.4.0 and all is compiled in 64-bit for AMD64. I have added a lot of feeds to Akregator and now it happens that when Akregator fetches the feeds it automatically marks all articles in these feeds as unread even if I marked them as read before. Feeds marked as read should stay this way and only new and unread articles should show as unread. |
From: Teemu R. <tp...@d5...> - 2005-03-19 18:09:38
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 tpr d5k net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW everconfirmed|0 |1 |
From: Teemu R. <tp...@d5...> - 2005-03-19 18:37:49
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 tpr d5k net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |UNCONFIRMED ------- Additional Comments From tpr d5k net 2005-03-19 19:37 ------- Umh, sorry, can't confirm this anyway. Read your description wrong and though this is same problem I have... |
From: Jure R. <jl...@ho...> - 2005-03-20 00:18:38
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From jlp holodeck1 com 2005-03-20 01:18 ------- I also noticed that no articles or even article titles are saved if I restart Akregator. I have in setting set to keep articles for no more then 10 days. |
From: Frank O. <fra...@kd...> - 2005-03-20 11:02:39
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 frank.osterfeld kdemail net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW ------- Additional Comments From frank.osterfeld kdemail net 2005-03-20 12:01 ------- Confirmed. Akregator confuses "Delete articles older than" and "Disable archiving" settings - that's because the mapping of the GUI buttons to the actual settings relies on the order the radio buttons are listed in the UI file(!). This definitely sucks. Everytime someone changes settings_archive.ui, he has to check manually if the order in the XML is still the correct one. I fixed this half a year ago, and now it's there again :-( |
From: Frank O. <fra...@kd...> - 2005-03-20 11:05:15
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 frank.osterfeld kdemail net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From frank.osterfeld kdemail net 2005-03-20 12:04 ------- CVS commit by osterfeld: fix the order of the buttongroup members. The mapping of button<->enum value is based on the order in the XML file! Unbelievable and error-prone. BUG: 101907 M +16 -16 settings_archive.ui 1.8 --- kdepim/akregator/src/settings_archive.ui #1.7:1.8 @ -43,12 +43,4 @ </property> </widget> - <widget class="QRadioButton" row="3" column="0" rowspan="1" colspan="2"> - <property name="name"> - <cstring>rb_DisableArchiving</cstring> - </property> - <property name="text"> - <string>Disable archiving</string> - </property> - </widget> <widget class="QRadioButton" row="1" column="0"> <property name="name"> @ -59,4 +51,20 @ </property> </widget> + <widget class="QRadioButton" row="2" column="0"> + <property name="name"> + <cstring>rb_LimitArticleAge</cstring> + </property> + <property name="text"> + <string>Delete articles older than: </string> + </property> + </widget> + <widget class="QRadioButton" row="3" column="0" rowspan="1" colspan="2"> + <property name="name"> + <cstring>rb_DisableArchiving</cstring> + </property> + <property name="text"> + <string>Disable archiving</string> + </property> + </widget> <widget class="KIntSpinBox" row="1" column="1"> <property name="name"> @ -85,12 +93,4 @ </property> </widget> - <widget class="QRadioButton" row="2" column="0"> - <property name="name"> - <cstring>rb_LimitArticleAge</cstring> - </property> - <property name="text"> - <string>Delete articles older than: </string> - </property> - </widget> <widget class="KIntSpinBox" row="2" column="1"> <property name="name"> |
From: Frank O. <fra...@kd...> - 2005-03-20 11:06:33
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From frank.osterfeld kdemail net 2005-03-20 12:06 ------- CVS commit by osterfeld: backport of archive settings fix (confusing disable archive and limit article age) CCBUG: 101907 M +10 -2 akregator_view.cpp 1.225.2.3 M +30 -3 articlelist.cpp 1.37.6.2 M +16 -16 settings_archive.ui 1.7.2.1 |
From: <ow...@bu...> - 2005-03-21 17:47:14
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 tpr d5k net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |spam.bucket free fr ------- Additional Comments From tpr d5k net 2005-03-21 18:47 ------- *** Bug 102113 has been marked as a duplicate of this bug. *** |
From: philou <ph...@ph...> - 2006-05-15 14:52:27
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From philou philou org 2006-05-15 16:52 ------- I have a similar problem with Google News RSS feeds: Everytime the feed refreshes, then all messages are marked as "new" again along with the new ones. Problematic feed here: http://news.google.com/news?ned=us&topic=h&output=rss Thanks Akregator 1.2.2 (KDE 3.5.2) Debian Sid |
From: Frank O. <fra...@kd...> - 2006-05-20 08:10:42
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From frank.osterfeld kdemail net 2006-05-20 10:10 ------- Caster: The problem with multiple items having the same guid is actually another problem and deserves its own bug report. (well, guids are meant to be unique _identifiers_ of items, so if a feed contains the same guid for different items, the feed needs to be fixed, not akregator). |
From: Frank O. <fra...@kd...> - 2006-05-20 09:19:39
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 frank.osterfeld kdemail net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Additional Comments From frank.osterfeld kdemail net 2006-05-20 11:12 ------- SVN commit 542756 by osterfeld: Do not reset status of modified articles to "New". It's just too much noise for a tiny bit of signal. BUG: 101907 M +4 -1 ChangeLog M +5 -3 src/feed.cpp --- branches/KDE/3.5/kdepim/akregator/ChangeLog #542755:542756 @ -6,14 +6,17 @ ----------------------------- New features: + 2006/05/01 add author information to article header (in the article pane only) -fo Bug fixes: + + 2006/05/20 Don't reset article status to New when the article changed (#101907) -fo 2006/05/10 Always show feed logos; load them on startup, not on first fetch -fo 2006/05/10 fix crash when using "Load the full website when reading articles" and an error (e.g. 404) is returned (#126812) -fo 2006/04/29 Do not crash on startup when Combined View mode is activated (Happened only when experimental tagging is -activated) -fo + activated) -fo 2006/03/22 Prevent "Akregator is running" messages on startup (reset PID to -1 when closing akregator) -fo Changes after 1.2.1: --- branches/KDE/3.5/kdepim/akregator/src/feed.cpp #542755:542756 @ -474,12 +474,14 @ if (!mya.guidIsHash() && mya.hash() != old.hash() && !old.isDeleted()) { mya.setKeep(old.keep()); + int oldstatus = old.status(); old.setStatus(Article::Read); + d->articles.remove(old.guid()); appendArticle(mya); - // reset status to New - if (!mya.isDeleted() && !markImmediatelyAsRead()) - mya.setStatus(Article::New); + + mya.setStatus(oldstatus); + d->updatedArticlesNotify.append(mya); changed = true; } |
From: radfoj <ra...@se...> - 2006-06-11 17:17:51
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From radfoj seznam cz 2006-06-11 19:17 ------- Sorry, I am little nervous with new akregator behaviour, so I did some mistakes. I wanted to say, that its important for me in many cases to be somehow informed, after article is UPDATED. Thanks |
From: radfoj <ra...@se...> - 2006-06-11 17:18:10
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From radfoj seznam cz 2006-06-11 19:11 ------- Its too technical here to understand many of post above. But I want reply to comment #47, which lead to changes in newest version of akregator (3.5.3): Do not reset status of modified articles to "New". Does this mean, that for e.g. http://www.kde.org/dot/kde-apps-content.rdf if new version of some application is released, akregator will not let me know about it? If so, I have many other feeds for which is crucial to be somehow informed, if article is informed. |
From: Caster <ca...@ma...> - 2006-06-19 21:53:47
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From caster matfyz cz 2006-06-19 23:53 ------- Exactly, I've just observed it with http://www.kde.org/dot/kde-apps-content.rdf - when you have an older version of app in your akregator archive, new version won't show up. It's the feed fault for publishing new article with same <guid> and bug should be filled for the feed. Before KDE 3.5.3, I think there were 3 possibilities a) feed contains two articles with same <guid> simultaneously (they are both present at one time), this resulted in those articles showing only as one, and updating status to NEW after EACH FETCH (until they were gone from the feed, replaced with newer articles). Now this was very annoying, because of the each fetch. Yeah it would need change of GUI/strings but I've read that KDE 3.5 is no longer strictly freezed because 4.0 is too far away, so it would be possible? b) feed contains article with same <guid> as some older one, not simultaneously with the new one. If the older one is archived in akregator, the new one overwrites it and sets NEW. This is what happens with http://www.kde.org/dot/kde-apps-content.rdf for example. c) feed is crazy and changes description/date/whatever each fetch, while keeping the same <guid>, annoying as a). This is case of google rss feeds? (not sure about that) 3.5.3 for sure made case b) not report such updated articles as NEW, while I think this bug and the real problem was about case a). 3.5.3 probably fixed all a) b) c) but at the cost of losing news from b). It would be possible to fix a) only though, probably not possible to fix c) without b). While it's clearly problem of the feeds to be broken, it's hard to get all of them fixed, especially if you can't know you missed an article and the feed is broken. What would be best is one global option for marking updated articles as NEW, and per-feed option overriding the global one. |
From: Caster <ca...@ma...> - 2006-06-19 21:55:29
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From caster matfyz cz 2006-06-19 23:55 ------- Sorry, in the previous comment I've put the last sentence in the wrong place. The sentence "Yeah it would need change of GUI/strings but I've read that KDE 3.5 is no longer strictly freezed because 4.0 is too far away, so it would be possible?" belongs to the end :) |
From: <ow...@bu...> - 2006-07-12 08:17:27
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 Stefan.Borggraefe gmx de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pupeno pupeno com ------- Additional Comments From Stefan.Borggraefe gmx de 2006-07-12 10:17 ------- *** Bug 130677 has been marked as a duplicate of this bug. *** |
From: Derek B. <au...@po...> - 2007-09-20 14:02:22
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=101907 ------- Additional Comments From auspex pointerstop ca 2007-09-20 16:02 ------- I don't understand - there's no sign that this has ever been fixed, even though it's marked RESOLVED and FIXED. Every feed I access has every post marked as NEW the first time it is fetched after kontact startup. It can't be anything to do with the feed itself changing, as I can fetch all feeds, mark everything as read, exit kontact, and start kontact again and all feeds will be refetched - and will be NEW. |