Make WordPress Core

Opened 7 years ago

Last modified 4 days ago

#43622 reviewing enhancement

Improve error messages

Reported by: peterwilsoncc's profile peterwilsoncc Owned by: audrasjb's profile audrasjb
Milestone: 6.8 Priority: normal
Severity: normal Version:
Component: General Keywords: has-patch
Focuses: ui-copy Cc:

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 (14)

#1 @netweb
7 years 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
7 years ago

  • Keywords ux-feedback added

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


6 years ago

#4 @JoshuaWold
6 years 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
6 years 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.

#6 @karmatosed
3 weeks ago

  • Keywords needs-patch added; ux-feedback removed
  • Milestone changed from Awaiting Review to 6.8

I am going to see how many of these we can get into 6.8 as already one is possible. We might have able to get a few more in. For now, removing ux-feedback as we have that going on in tickets and the feedback is already that we agree these should be done. I am slightly less keen to have one ticket for these all unless we have actions come out of this ticket or a patch. So for now let's put needs-patch onto this to also get some here.

#7 @sabernhardt
3 weeks ago

  • Focuses ui-copy added

This ticket was mentioned in PR #8177 on WordPress/wordpress-develop by @sukhendu2002.


2 weeks ago
#8

  • Keywords has-patch added; needs-patch removed

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


2 weeks ago

#10 @audrasjb
2 weeks ago

  • Keywords has-patch removed

Hi @sukhendu2002 thanks for the PR! Is it ready for review? Thanks!

#11 @sukhendu2002
2 weeks ago

I’ve added a few more error messages and have marked it ready for review now. Thanks!

@sukhendu2002 commented on PR #8177:


12 days ago
#12

Hi @joedolson thanks for the review. I've made the suggested changes. Let me know if anything else is needed!

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


4 days ago

#14 @audrasjb
4 days ago

  • Keywords has-patch added
  • Owner set to audrasjb
  • Status changed from new to reviewing

Thanks for addressing the requested changes. The PR looks good to me now.

Note: See TracTickets for help on using tickets.