Last modified: 2012-02-28 21:42:08 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 26746 - Document all caches and how to clear them
Document all caches and how to clear them
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
1.18.x
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: documentation
  Show dependency treegraph
 
Reported: 2011-01-15 13:33 UTC by Niklas Laxström
Modified: 2012-02-28 21:42 UTC (History)
4 users (show)

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


Attachments

Description Niklas Laxström 2011-01-15 13:33:34 UTC
Mostly self-obvious... there should be an overview of all possible caches, and how to purge them manually. This is a problem for developers and users alike.
Comment 1 Mark A. Hershberger 2011-01-22 01:00:35 UTC
But *who* knows enough of this information to document it?
Comment 2 Roan Kattouw 2011-01-24 01:44:44 UTC
(In reply to comment #1)
> But *who* knows enough of this information to document it?
Different people know different things, I guess. Grepping the code for wfMemcKey should catch like 90% of all instances where we use caching.

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


Navigation
Links