WordPress.org

Make WordPress Core

Opened 19 months ago

Last modified 7 months ago

#43622 new enhancement

Improve error messages

Reported by: peterwilsoncc Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: General Keywords: ux-feedback
Focuses: Cc:
PR Number:

Description

Audit and improve error messages throughout core.

Many errors contain generic text (something went wrong, expired link warnings) without further explanation, in these cases further details can be added.

Others could do with a wholesale rewrite to improve clarity for non-technical users and/or shift blame away from the user - Slow down cowboy, no need to check for new mails so often!, for example.

Follow up to #38332, related #43617.

Change History (5)

#1 @netweb
19 months ago

Here's a few more related tickets:

#16243 Unhelpful error messages when updating default category
#28845 Better error messages when uploading theme as plugin and vice versa
#33374 Improvements for the messages visible in the plugin manager
#38669 Standardize "found in trash" messages
#41142 Theme editing: inconstancies with messages between this and plugin editing
#42269 i18n: Unify permission error messages for content
#42735 Add missing periods to some error messages
#42945 Not all error messages are capitalized

#2 @karmatosed
19 months ago

  • Keywords ux-feedback added

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


8 months ago

#4 @JoshuaWold
8 months ago

We just discussed this in our #design triage. It'd be exciting if this could be a focus for an upcoming release!

The next step here is likely compiling a list of the current error messages as a start.

#5 @mrtortai
7 months ago

This confirmation page is very useful - it confirms that the user does indeed want to log out.

https://i.stack.imgur.com/8nkm1.png

However the, "something went wrong" page title is unnecessarily concerning, and using alternative wording (e.g., "Do you really want to log out?") would be much more effective.

Note: See TracTickets for help on using tickets.