Last modified: 2010-05-15 15:48:30 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 T10842, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8842 - $wgFeedLimit and $wgFeedDiffCutoff seem to do nothing
$wgFeedLimit and $wgFeedDiffCutoff seem to do nothing
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.9.x
PC Windows 98
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-01 02:04 UTC by Invalid Account
Modified: 2010-05-15 15:48 UTC (History)
1 user (show)

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


Attachments

Description Invalid Account 2007-02-01 02:04:25 UTC
$wgFeedLimit = 2;
$wgFeedDiffCutoff = 2;

In localsettings.php

Well this should make there less RSS/Atom feeds. Well I tried all sorts of variations and it appears 
these settings don't do a thing. They are mentioned in defaultsettings.php in that they're supposed to 
reduce how much at a time is in a feed and the second is too keep certain large sized things out of the 
feed.
Comment 1 Brion Vibber 2007-02-02 19:05:56 UTC
Keep in mind that feeds are aggressively cached by default.
Try setting $wgFeedCacheTimeout = 0; to experiment more quickly.
Comment 2 Invalid Account 2007-02-03 09:33:25 UTC
With "$wgFeedCacheTimeout = 0;" the setting $wgFeedDiffCutoff works, however $wgFeedLimit still has 
no effect at all neither able to increase nor decrease the feed size. 
Comment 3 Aaron Schulz 2008-05-16 20:35:29 UTC
Looks like the individual feeds need to check this. Grepping shows that only RC does :(
Comment 4 Aaron Schulz 2008-05-16 21:35:07 UTC
Fixed in r34942

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


Navigation
Links