Last modified: 2014-10-25 00:51:40 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 13108 - Warn on edit summaries containing redlinks
Warn on edit summaries containing redlinks
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 5019
  Show dependency treegraph
Reported: 2008-02-22 15:57 UTC by Paolo Liberatore
Modified: 2014-10-25 00:51 UTC (History)
2 users (show)

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


Description Paolo Liberatore 2008-02-22 15:57:25 UTC
In some cases, one may want to enter an edit summary with a redlink, but this is more often the result of a mistake. Since edit summaries cannot be fixed at a later moment, I believe it would be nice to have (as a user preference) an option of being requested confirmation when entering an edit with a summary containing a redlink. This would be similar to the "null summary" check, so that the user could stilll decide to commit the edit anyway.
Comment 1 Andre Klapper 2014-06-22 18:09:54 UTC
(In reply to Paolo Liberatore from comment #0)
> In some cases, one may want to enter an edit summary with a redlink

Is this basically a request for "templates and links in summaries should be rendered on editing" (hence parsed), as a first step required to warn on redlinks? In that case, this would depend on bug 5019 I guess?

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