Rewrite an error message for humans
Turns a technical error into one a non-technical user can act on, without inventing a cause the log does not support.
Rewrite the error message below for someone who is not technical.
Say what happened, whether their work was lost, and exactly what to do next. Two sentences at most. No apology, no jargon, no error codes in the visible text.
If the original message does not say whether data was lost, do not guess - leave that out.
--- original ---
{{error}}Fill these in
| Placeholder | What goes here | Example |
|---|---|---|
| {{error}} | Raw error text | SQLSTATE[HY000] [2002] Connection refused |
Notes from the author
The last rule stops the most common failure, which is a reassuring "nothing was lost" that turns out to be false. Works unchanged everywhere.
Worked example
SQLSTATE[HY000] [2002] Connection refusedWe could not save your changes because the connection dropped. Check your internet and press Save again.Tagged