Last modified: 2011-03-13 18:04:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T16878, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14878 - Annoying template vandalism
Annoying template vandalism
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-21 17:16 UTC by blah
Modified: 2011-03-13 18:04 UTC (History)
3 users (show)

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


Attachments

Description blah 2008-07-21 17:16:56 UTC
Given the annoyance of the now rampant template vandalism (or more specifically, the annoyance of countless anons pestering us about it for half an hour after each spat is dealt with) it seems to me it would be efficient if registered users (or perhaps administrators only, or an even stricter set of users if this has too much potential to drain system resources) were given the ability to cause a cascading purge of the server cache, whereby the recaching of a template recached every page that transcluded that template, so on and so forth.
Comment 1 Roan Kattouw 2008-07-21 20:48:23 UTC
Anyone can actually do this by editing or purging (not sure about the last one) a template, that'll schedule all transcluding pages to be purged. They aren't purged immediately because there could very well be millions of transcluding pages (this is true for [[Template:!]], for example) and purging them all would take way too long for a simple request. I don't see how we can resolve this bug except by adding some sort of job queue management interface for sysops, which would allow them to remove and prioritize jobs.
Comment 2 Chad H. 2008-07-21 22:03:59 UTC
The job queue was designed to keep large operations such as this from being done all at once. As soon as you try to override that, you defeat the purpose of the cache to begin with. 

I think having an interface to prioritize jobs kinda ruins the simplicity and transparency of the job queue. Suggest WONTFIX.
Comment 3 Siebrand Mazeland 2008-08-11 12:30:44 UTC
WONTFIX per demon.

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


Navigation
Links