Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
Page History
...
Banner is the best choice for sever severe errors because the system stores message and it can be forwarded and analyzed further.
| Severity | Message type | Send to |
|---|---|---|
| Critical errors (exceptions) | Banner | Logged-in user |
| Severe errors (exceptions that leave the app in a bad state) | Banner | Logged-in user, administrator |
| Security breaches or similar | Banner | Administrator |
Show alerts when it's enough that the user sees the error
...
| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Alert captures the user's attention
Notification is too easy to miss.
Never use a notification to signal errors. Notifications are too easy to miss. Instead, put more effort on validation before kicking off the action. You should only use a notification to confirm that an action was aborted. For example, if the user uploads a file and decides to cancel the running upload, it's OK to show a notification to confirm that the upload was aborted. The user can also determine that the upload was cancelled by looking at the UI: no progress bar anymore but also no uploaded files.
...
Overview
Content Tools