Last modified: 2008-03-18 18:43:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13403 - New flags are not immediately visible in version history
New flags are not immediately visible in version history
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-03-17 19:29 UTC by P. Birken
Modified: 2008-03-18 18:43 UTC (History)
1 user (show)

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


Description P. Birken 2008-03-17 19:29:59 UTC
If you flag a version, the flag dows not become visible in the version history immediately, but only after a few minutes. This does not seem to be the case for automatically flagged versions, only if you flag manually.
Comment 1 Aaron Schulz 2008-03-18 03:55:16 UTC
This is a general problem, and revisiondelete has it too. Histories tell the client to use the cache as long as it is after the last edit timestamp. Since revision deletions and taggings don't change that, it doesn't tell the client cache to clear.

It might be nice to make a sort of generalized cache timestamp table for this stuff.
Comment 2 Brion Vibber 2008-03-18 18:26:19 UTC
Er, isn't that was page_touched is for?
Comment 3 Aaron Schulz 2008-03-18 18:28:02 UTC
(In reply to comment #2)
> Er, isn't that was page_touched is for?

Not at all :)

That is for cache-related reasons. It could be changed many times without the history actually changing (like pressing a purge tab), so the history relies only on the last revision timestamp.
Comment 4 Brion Vibber 2008-03-18 18:33:16 UTC
The last revision timestamp is insufficient to serve as a cache invalidation timestamp for history view -- revisions older than the latest may be deleted, undeleted, or imported.

These events would (or *should*!) update page_touched, however.
Comment 5 Aaron Schulz 2008-03-18 18:34:31 UTC
OK, so then this bug is now a matter of changing how it works (use page_touched). Shouldn't be that difficult then.
Comment 6 Aaron Schulz 2008-03-18 18:43:13 UTC
Fixed in r32119.

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