Bug 161786 - Articles are connected to URL instead of <internal_index>
Summary: Articles are connected to URL instead of <internal_index>
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: 2008-05-08 11:40 UTC by gapon
Modified: 2017-01-07 21:57 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gapon 2008-05-08 11:40:48 UTC
Version:           1.2.9 (using 3.5.9, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.25-gentoo-r2

Steps to reproduce:
- add new channel with the name "My RSS" and URL "http://whatever.com/rss"
=> articles are fetched, OK
- change the URL to "http://whatever.com/rss_ng"
=> all the articles are still there, OK, just new RSS URL provided so one changes it
- restart Akregator
=> all the articles of "My RSS" are gone - WHY???!!!

I think user definitely knows what (s)he does so articles should be there (it is still "the same" RSS feed for her/him).

If web server changes its RSS URL, one has to keep the old channel in Akregator and add a new one in order to not lose her/his old articles (please note that they can be important).

Thanks.
Comment 1 Frank Osterfeld 2008-05-08 11:58:27 UTC
Yes, that's an issue, we'll address that when moving to Akonadi (4.2)
Comment 2 Denis Kurz 2016-09-24 19:43:11 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 3 Denis Kurz 2017-01-07 21:57:58 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.