Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Handle abuse filter warnings/errors #182
An abuse filter warning is currently an irrecoverable error. API will return something like:
<?xml version="1.0"?><api><edit code="abusefilter-warning-codespill" info="Hit AbuseFilter: Extraneous formatting" warning="<table [...]" result="Failure" /></api>
(warning HTML truncated).
I imagine Twinkle should display that warning and allow the user to try again (not sure what the mechanism for that is)
added a commit
Oct 20, 2013
The only problem with that commit is that all is lost when an AbuseFilter warning is hit. The edit should be retried automatically (as happens for edit conflicts) if the editor chooses to retry. The problem lies in providing the choice to the user. I seem to remember that AzaToth is quite keen to see the Status system overhauled, and some kind of status-based prompt could be implemented as part of any such future overhaul.