Last modified: 2007-04-24 02:48:09 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 4568 - Autogenerate sensible deletion reasons for longer pages
Autogenerate sensible deletion reasons for longer pages
Status: RESOLVED DUPLICATE of bug 9656
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-01-11 22:06 UTC by Tomer Chachamu
Modified: 2007-04-24 02:48 UTC (History)
0 users

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


Description Tomer Chachamu 2006-01-11 22:06:50 UTC
If an article is long, its deletion reason will be blank by default.

How about:

content began: '[30 characters or so]...' (583 bytes) (and the only contributor...)

Obviously configurable through the MediaWiki: namespace
Comment 1 Aaron Schulz 2007-04-24 02:46:16 UTC
Not really that useful. Saying "content was 'I am a gay homo' and only
contributor..." is much stronger than some word/byte count. If it is not an
obviously very short vandal page, saying it is "short" or how many bytes is has
is not very useful, as you will still need to look it over.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-04-24 02:48:09 UTC
Bug 9656 is the straightforward way of doing this, and that's now fixed on 

*** This bug has been marked as a duplicate of 9656 ***

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