Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Error Messaging for Invalid URLs #8460

Closed
SiobhyB opened this issue Oct 21, 2018 · 11 comments · Fixed by #9645
Closed

Better Error Messaging for Invalid URLs #8460

SiobhyB opened this issue Oct 21, 2018 · 11 comments · Fixed by #9645
Assignees

Comments

@SiobhyB
Copy link
Contributor

SiobhyB commented Oct 21, 2018

Expected behavior

If I enter an invalid URL at the login form, I expect to receive an informative, helpful error message that informs me why I'm not able to log into the app.

Actual behavior

The following error appears if I enter an invalid URL at the login form, which isn't that helpful to users:

"Couldn't connect to WordPress site. There is no valid WordPress site at this address. Check the site address (URL) you entered."

Screenshot:

screenshot_20181021-215621

Steps to reproduce the behavior

  1. Navigate to the app's login screen and select the "Log in by entering site address" option.
  2. Enter some nonsense text, for example "DFOJDOFJF".
Tested on Pixel, alpha-132 of WordPress for Android

This was raised by @jtreanor and some other recent support rotations as a lot of support requests are made up of users who enter an invalid URL. More informative error messaging could have a positive impact on the number of incoming requests.

iOS version of this issue is here: wordpress-mobile/WordPress-iOS#10294

@thehenrybyrd
Copy link
Contributor

Ran into this in #1648733-zen, where the user had entered the URL "Santara Net Review".
It would be great to produce an error that states this isn't a URL, and gives an example of a URL.

@thehenrybyrd
Copy link
Contributor

Another in #1666486-zen - the user entered "La vie d'una Maison"

@thehenrybyrd
Copy link
Contributor

#1667453-zen - the user entered "Datos".
Looks like some folks don't understand they need a "domain.tld" format for this to work. They're entering the name/title of their site, instead.

@thehenrybyrd
Copy link
Contributor

#1693402-zen, entered "mcgospelentertainment".

@thehenrybyrd
Copy link
Contributor

Here's another who entered "Estanislao Mallofre Jane". #1749121-zen

@rachelmcr rachelmcr added this to To Do in Groundskeeping via automation Feb 15, 2019
@thehenrybyrd
Copy link
Contributor

Another example here in #1834758-zen

notaurl

@thehenrybyrd
Copy link
Contributor

Another case in 1899497-zen. They've entered an apparently random sequence of numbers and letters.

@thehenrybyrd
Copy link
Contributor

Another in 1923800-zen. Again, a random-looking sequence of numbers and letters.

@designsimply
Copy link
Contributor

Raising in priority due to the number of user reports referenced.

@designsimply designsimply moved this from To Do to Prioritized Android in Groundskeeping Apr 9, 2019
@thehenrybyrd
Copy link
Contributor

Thanks Sheri!
I ran into another of these today in 1949634-zen.
Folks seem to think they can just type in relevant search terms.
I blame Google 😆

@oguzkocer oguzkocer self-assigned this Apr 15, 2019
@oguzkocer oguzkocer moved this from Prioritized Android to In Progress in Groundskeeping Apr 15, 2019
@elibud elibud added the Design Needed A design solution is needed. label Apr 16, 2019
@oguzkocer
Copy link
Contributor

oguzkocer commented Apr 16, 2019

I have made a design request for this and already received some tips. I also requested a copy for it. Once I get the copy, I'll open a PR for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Groundskeeping
  
Done April 15 - 19, 2019
Development

Successfully merging a pull request may close this issue.

5 participants