Last modified: 2011-04-14 15:10:39 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 8649 - Hooks needed for metadata tracking
Hooks needed for metadata tracking
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 8136 8560
  Show dependency treegraph
Reported: 2007-01-16 03:31 UTC by Andrew Dunbar
Modified: 2011-04-14 15:10 UTC (History)
0 users

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


Description Andrew Dunbar 2007-01-16 03:31:16 UTC
Some extensions need to track metadata based on changes to articles and titles.

Some of these changes are not trivial to track and each extension will have to
reinvent the wheel.

* Article creation by any means (including undelete)
* Article deletion by any means (revert? rollback?)
* Title move by any means (revert? rollback?)

Some extensions only care about articles and not redirects, some only care about
the main namespace:

* Article namespace change
* Article becomes redirect (via editing, reverting)
* Redirect becomes article (via editing, reverting)

Currently it's only possible to catch some of these changes by hooking two
functions and tracking state between them.
Comment 1 Andrew Dunbar 2007-02-09 23:13:48 UTC
Tim Starling has suggested on IRC a couple of days ago that the RecentChange
class might be the solution.

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