Page MenuHomeMiraheze

Recentchanges 15552000 seconds hard to understand
Closed, ResolvedPublic

Description

On e.g., https://meta.miraheze.org/wiki/Special:ManageWiki/settings#mw-section-edit

RecentChanges max age
15552000
Items in the recentchanges table are periodically purged; entries older than this many seconds will go.
Active User Days
30
The number of days within which a person must make edits to be considered an "active" user.
Restriction Types
	Edit
	Move
	Create
	Upload
	Delete
	Protect
Actions that can be restricted.
RecentChanges link days
	1
	3
	7
	14
	30
	180
List days options to list in the Special:Recentchanges and Special:Recentchangeslinked pages.
  1. The two Recentchanges sections are separated by a non-Recentchanges section. They should be joined.
  2. The first Recentchanges section uses units: seconds. The second Recentchanges section uses units: days. They should use the same units, days. Or at least the form should help them compute that
$ expr 15552000 / 60 / 60 / 24
180

Event Timeline

Jidanni triaged this task as Low priority.Dec 9 2019, 02:46
Jidanni created this task.

Maybe just add a comment "15552000 seconds = 180 days" to help the user along, at least.

Maybe just add a comment "15552000 seconds = 180 days" to help the user along, at least.

Would a help guide with a table for common values be good on meta + linked?

OK. Use something like

Days Seconds
   1 86400
   3 259200
   7 604800
  14 1209600
  30 2592000
 180 15552000

that I made with perl program

print "Days Seconds\n";
for (qw/1 3 7 14 30 180/) {
    printf "%4d %d\n", $_, $_ * 60 * 60 * 24;
}

Anyone can create that page on meta then!

But then that page needs to be linked from all wikis' Special:ManageWiki/settings#mw-section-edit 's.

We can do that after it is created.

As a matter of fact, 180 days is not enough. Especially for sites meant as historical archives.
On my wiki farm I used to have in Local_Settings.php:

switch ($wgSitename)
{
    case 'ABJ':
        $i = 14;
    break;
    default:
        $i = 9;
}
unset($wgRCLinkDays);
foreach (range(0, $i) as $j)
{
    $wgRCLinkDays[] = pow(2, $j);
}
$wgRCMaxAge = 3600 * 24 * ($wgDefaultUserOptions['rcdays'] = end($wgRCLinkDays));

A pretty major part of the reason I've seen cited for having certain information "expire", for lack of better word, is due to the fact that the servers have been known to run out of space or memory. Part of managing this problem is clearing old and likely unused, uncontroversial, and irrelevant data. It's really just working out kinks wherever possible in the least obstructive and destructive ways that are plausible enough.

PlavorSeol assigned this task to Jidanni.
PlavorSeol subscribed.

Closing this task as the commit is merged.