Manual:$wgRCMaxAge
| Recent changes, new pages, watchlist and history: $wgRCMaxAge | |
|---|---|
| Items in the recentchanges table are periodically purged; entries older than this many seconds will go. |
|
| Introduced in version: | 1.4.0 (r7170) |
| Removed in version: | Still in use |
| Allowed values: | (positive integer) |
| Default value: | 90 * 24 * 3600 (90 days) (1.25+) 13 * 7 * 24 * 3600 (13 weeks) (1.16-1.24) |
| Other settings: Alphabetical | By function | |
Details
[edit]This setting holds the length that recent changes history should be retained for (in seconds).
Whenever anything happens on the wiki (e.g. page edit, move, delete, new user, etc.) a row is added to the recentchanges table giving details about the change. Periodically any entries that are older than the length of time given by this setting are removed from the table, and therefore from the list of recent changes.
If no hook for ArticleEditUpdatesDeleteFromRecentchanges returns false, there is a 1% chance that the recent changes table will be purged.
Changing this value won't suddenly allow you to see more entries on the recent changes page, as the changes have already been removed from the table.
However any entries that are still in the table will not expire until the new limit is reached and the changes get purged.
If you want to re-populate the recentchanges table having changed this setting, then you need to run maintenance/rebuildrecentchanges.php.
Note that running this script marks all previously patrolled edits as unpatrolled.
Setting $wgRCMaxAge to a value such that $wgDefaultUserOptions['rcdays'] > ceil($wgRCMaxAge/24*3600) (i.e. setting the default number of days to display to be greater than the number of days to retain) may trigger errors on the wiki, such as when viewing user preferences pages.
Affected pages
[edit]This parameter affects recent changes, related changes, watchlists, and list of new pages, but not history and user contributions pages.