This bug was initially created as a clone of T31200; Brion wrote:
Workarounds for failures to handle error conditions in the JavaScript code exist.
The error info from the dieUsage appears to perfectly correctly make it back to
the 'doneCallback' function in 'handleAJAXSave' (via the actual call in
liquidThreads.doNewThread ).
However, doneCallback tries to handle error conditions by submitting the same
form as non-Ajax in the hopes that that code path will show an error as well,
which apparently isn't ending up having the expected results.
It should instead probably show the error message directly.....?
Does this need more general or more specific handling for particular kinds of errors that we can't report back cleanly through this interface?
Edit: use of dieUsage was removed in 2018 in e51c8501b4656007fef0e1a8e8b3dd44caface26
Version: unspecified
Severity: major
URL: http://www.mediawiki.org/wiki/Extension:LiquidThreads