Bawolff <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |
         Resolution|                            |WORKSFORME

--- Comment #1 from Bawolff <> 2011-02-03 20:34:17 UTC ---
Can not reproduce on trunk. (While once i disable $wgUseRCPatrol, which messes
with last mod header)

However, if the update script makes any edits (and those edits get included in
the RC, perhaps hidden as bot), which might happen if it deletes old messages
that are the same as the default (but that'd only be updating from a really old
version), that would obviously reset the timestamp as it should)

>Understand that many programs e.g., WWWOFFLE, monitoring this date will
>thus cause a false notification to their user, who then looks to find
>nothing changed in RecentChanges.

The last-modified date could mean anything changed, not necessarily someone
edited. For example installing an extension (which will touch the modified time
on LocalSettings.php, and in the default config update $wgCacheEpoch) will also
reset this date. Changing your user prefs will also update this date (because
that can affect what the RC looks like). If you want to know when the last
person edited, you should use the date of when the last person edited, not the
date that page changed.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to