Bug 130951 - aKregator should default to the feed-specified check interval
Summary: aKregator should default to the feed-specified check interval
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: feed parser (show other bugs)
Version: 1.2.2
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2006-07-17 02:03 UTC by Stephan Sokolow
Modified: 2018-10-13 09:50 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 Stephan Sokolow 2006-07-17 02:03:56 UTC
Version:           1.2.2 (using KDE KDE 3.5.2)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9) 
OS:                Linux

When a feed specifies an interval for update checking, aKregator should use it as the default. As of aKregator 1.2.2, it apparently uses the global check interval as default regardless of what the feed specifies.
Comment 1 Frank Osterfeld 2006-08-20 22:13:30 UTC
Right, this is mostly a problem of the parser, as the information is not parsed by librss (skipDays and skipHours are, but other formats are not).
Comment 2 Adrián Chaves (Gallaecio) 2012-09-30 19:50:51 UTC
In Akregator 4.9.2, when you add a new feed, you can define whether to use the default Akregator interval, or a custom interval for the feed.

If I understand the issue right, against the latest Akregator version, this would mean that, when adding a new feed, in case the feed defines an update rate, that update rate should be enabled by default, instead of Akregator‘s. Is that right?

Also, can you provide a link to a news feed that suggest an update interval, in order to confirm this is not already the case, and test the feature when implementing it?
Comment 3 Andrew Crouthamel 2018-09-23 02:19:06 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 4 Stephan Sokolow 2018-10-13 09:47:32 UTC
Sorry for the delay.

It appears to still be a problem under Akregator 4.13.3.

If you want me to test under KDE 5, let me know and I'll try to get access to a machine running something newer than Kubuntu 14.04 LTS.

You can use http://feeds.ssokolow.com/ssokolow_blog?format=xml for testing.

It's handled by FeedBurner and provides the following RSS 1.0 elements:

<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>

(Where xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" )

If you also need something to test against which uses RSS 2.0's `ttl` element, let me know and I'll dig something up or craft a test case.
Comment 5 Stephan Sokolow 2018-10-13 09:50:18 UTC
Woops. Forgot to set the status.