[wp-meta] [Making WordPress.org] #5590: Improve messaging on login.wordpress.org

[Making WordPress.org]

#5590: Improve messaging on login.wordpress.org
------------------------------------+---------------------
 Reporter:  Otto42                  |       Owner:  (none)
     Type:  task                    |      Status:  new
 Priority:  normal                  |   Milestone:
Component:  Login & Authentication  |  Resolution:
 Keywords:                          |
------------------------------------+---------------------

Comment (by dd32):

 Replying to [ticket:5590 Otto42]:
 > 1. On the login page, we have the WordPress.org logo instead of the
 normal one, but no messaging indicating where they are. Idea: Add in some
 text right there, before they login.

 There was messaging on the login landing page, but not once they proceeded
 to attempt to login. [10845] added that text to the wp-login.php pages
 too.

 > 2. On the error message: detect common username cases like "admin" and
 provide better info. Yes, the "admin" account is blocked on org and will
 be forever, so nobody will ever use it legitimately, so they are obviously
 in the wrong place and should be told so and where to properly go to most
 likely help them.
 > Result: "ERROR: Your account has been disabled. Please contact forum-
 password-resets at wordpress.org for more details."

 Added a much more specific error in [10844] in line with the WordCamp
 messaging, not fully set on it, but it's much better than what was there.
 `*Are you in the right place?* This login form is for the WordPress.org
 website, rather than your personal WordPress site.`


 > 3. Similar for username does not exist cases. Different messaging
 perhaps, tell them to try their email address instead or something.

 The existing error message here was horrible - but did tell them to try
 their email (or at least that's what it was trying to do), I've filed
 #core52915 to change it upstream, and added a more specific WordPress.org
 variant in [10850]

 I've also filed #core52914 to fix the inconsistent error message formats
 with/without the `<strong>Error:</strong>` prefix.

 > While we're at it, improve the existing messages as well.

 The majority of the error messages come from Core rather than
 WordPress.org, but I agree that they need reworking. See #core52914 for a
 listing of all the various error messages that can be encountered. [10850]
 includes some error overwriting abilities, so if you're aware of other
 errors that should be reworked more urgently on WordPress.org to reduce
 the support load, let's do it.

 I think this is probably enough to mark this as closed for WordPress.org?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5590#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org