[wp-trac] [WordPress Trac] #52392: Improve "critical error" language
WordPress Trac
noreply at wordpress.org
Thu Jan 28 21:45:34 UTC 2021
#52392: Improve "critical error" language
-------------------------+-----------------------------
Reporter: Ipstenu | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Site Health | Version:
Severity: normal | Keywords:
Focuses: |
-------------------------+-----------------------------
There has been a notable uptick in people coming to WordPress.org when
they get the message:
> There has been a critical error on this website. Please check your site
admin email inbox for instructions.
> Learn more about debugging in WordPress.
The link goes to https://wordpress.org/support/article/debugging-in-
wordpress/
That actually has begun to encourage people to log in to WordPress.org,
which would be fine _except_ they're trying to log in as the account they
use on their self-hosted version of WordPress. Which fails.
While we're working on improving the messaging when a login fails, maybe
we could also do a better job of making sure people know that you cannot
log in to WordPress.org with the credentials from your own host.
I know we're trying to balance 'too much info!' on that page, but this is
a pretty common point of confusion.
Just to give a metric here, the numbers went from 1-5 a week to 12-20 a
day (yes, a day) asking why their account is banned (for people who use
'admin') or non-existent. This is clearly creeping up pretty fast. We've
already updated the replies we use to explain, and that seems to be
sufficient to help them once they're there, but it would be long-term
better that they didn't have to wait on someone to reply.
See also: https://meta.trac.wordpress.org/ticket/5590
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52392>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list