Last modified: 2010-05-15 15:32:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T3754, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1754 - only one timestamp for two feeds (Atom, RSS)
only one timestamp for two feeds (Atom, RSS)
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
1.4.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-reviewed
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-25 13:58 UTC by Roger Luethi
Modified: 2010-05-15 15:32 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Proposed patch against CVS HEAD (670 bytes, patch)
2005-04-22 14:29 UTC, Anders Wegge Jakobsen
Details
Patch agaist CVS REL1_4 (683 bytes, patch)
2005-04-23 11:32 UTC, Anders Wegge Jakobsen
Details

Description Roger Luethi 2005-03-25 13:58:29 UTC
RSS and Atom feeds for RecentChanges are read from objectcache if the cache is
current or the cache is not older than $wgFeedCacheTimeout. There is only one
timestamp variable ($wgDBname:rcfeed:timestamp) in the objectcache for both
feeds, though.

Thus, if one of the feeds, say RSS, gets pulled and updated, the other one is
also marked current even though it wasn't touched. On a low-traffic
installation, this can cause substantial delays (several hours) until the
'losing' feed gets updated.
Comment 1 Anders Wegge Jakobsen 2005-04-22 14:29:21 UTC
Created attachment 446 [details]
Proposed patch against CVS HEAD
Comment 2 Anders Wegge Jakobsen 2005-04-23 11:32:35 UTC
Created attachment 450 [details]
Patch agaist CVS REL1_4
Comment 3 Ævar Arnfjörð Bjarmason 2005-04-23 21:47:53 UTC
Fixed in REL1_4 and HEAD, thanks for the patch.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links