Last modified: 2014-02-12 23:37:59 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 T19822, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 17822 - AbuseFilter warning page should display original page text
AbuseFilter warning page should display original page text
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-03-06 23:38 UTC by Ryan Schmidt
Modified: 2014-02-12 23:37 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ryan Schmidt 2009-03-06 23:38:59 UTC 
Currently in AbuseFilter, doing an action that triggers a warning keeps one on the edit page, but their version that they tried to save is shown in the edit box. Requesting that an interface like edit conflicts be used so that they may re-modify the original text if they so wish without needing to refresh the page (have a notice saying the original text is on top, their changed text on the bottom, and only the top will take effect when saved -- basically the same interface used for an edit conflict, just with the AbuseFilter warning prepended to it).
Comment 1 MacGyverMagic 2009-03-10 09:43:21 UTC 
*** Bug 17903 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Garrett 2009-03-12 11:42:57 UTC 
Might be more sensible to make the change in core so it happens with SpamBlacklist et al too.
Comment 3 Andrew Garrett 2009-07-16 16:47:48 UTC 
Marking this bug as Lowest priority.

I've done this in a batch to (usually enhancement request) bugs where:
* It is not clear that this bug should be fixed.
* It is not clear how to fix this bug.
* There are difficulties or complications in fixing this bug, which are not justified by the importance of the bug.
* This is an extremely minor bug that could not be fixed in a few lines of code.

If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
Comment 4 Waldir 2009-10-21 09:19:48 UTC 
(In reply to comment #2)
> Might be more sensible to make the change in core so it happens with
> SpamBlacklist et al too.
> 

FYI, that's requested on bug 9416.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links