Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.4k stars 1.98k forks source link

New site: Some Brazilian users can't choose a free subdomain #46752

Open davipontesblog opened 3 years ago

davipontesblog commented 3 years ago

There are some reports from Brazilian users in the support forum that there is no way to create a site with a free subdomain for them. This is not easy to reproduce, so, so far we have collected the following information:

Steps to reproduce

  1. Starting at URL: https://wordpress.com/start/domains
  2. Pick a domain name

What I expected to see

There should be a free domain option to choose from:

Screen Shot 2020-10-23 at 20 11 48

What happened instead

The option is not available.

Reports

Screen Shot 2020-10-19 at 08 59 18

@eduardozulian found out that at the domain step it seems we allow only numbers, which could be a reason why. From https://wordpress.com/typo/?subdomain=111111

The address 111111.wordpress.com cannot be registered. Sorry, site names must have letters too! But you can sign up and choose another one.

One user replied and @carinapilar found out it doesn't seem it's happening only with numbers :sweat:

ENgrmX

Could this be related to A/B testing?

Context / Source

user-report

https://wordpress.com/br/forums/topic/achei-que-fosse-gratuito/ https://wordpress.com/br/forums/topic/nao-consigo-lancar-site https://wordpress.com/br/forums/topic/novos-blogs/

davipontesblog commented 3 years ago

@niranjan-uma-shankar would this issue be better prioritized under the Martech repo?

niranjan-uma-shankar commented 3 years ago

It can continue to be in the Calypso repo, but I'll add it to the MarTech board. Thanks!

niranjan-uma-shankar commented 3 years ago

I'm able to consistently reproduce the error with the example shown in the screenshot 123134134134. I've seen an earlier report in https://github.com/Automattic/wp-calypso/issues/38878, not sure if it's related.

@Automattic/cobalt Is this something your team could look into? Please let me know if you think MarTech should own this.

For the second screenshot posted in the PR description for the pessoinhastorehome.wordpress.com, I wonder if that user has been flagged as a spam user? We've seen before that for such users, the free subdomain suggestion does not show up, reported earlier in p1601550702020300-slack-marketing.

cc @klimeryk @daledupreez

daledupreez commented 3 years ago

@Automattic/cobalt should definitely be involved here.

I think we have at least two possible work items here:

  1. Numeric-only searches - we should show an error message or warning for that specific case (at least if we're retrieving free suggestions)
  2. Better error handling for cases where a user isn't permitted to make purchases or create new sites.
niranjan-uma-shankar commented 3 years ago

Thanks, I'll remove it from MarTech's board then.

lsl commented 3 years ago

This is preventing free users from launching if they happen to make a domain search in the launch flow (search results wipe out the skip purchase option by not rendering it.)

I'm currently on rotation, and came across a couple of users with this issue, I put a draft PR up in #47663 that fixes the issue cosmetically, but needs a bit of testing / hooking up the site id props for each scenario to make the button work properly.

I don't really know enough about this and should probably be focusing on my rotation right now, would someone with more context from cobalt / martech be able to look at this?

lsl commented 3 years ago

Ah sorry, @daledupreez pointed out this is probably a separate issue causing similar outcomes. New ticket incoming :smile:

daledupreez commented 3 years ago

New issue is #47664.

carinapilar commented 3 years ago

Adding this P2 post here too: p58i-9Lm-p2. It seems we can go ahead and close this issue.

daledupreez commented 3 years ago

@carinapilar, the issue addressed by that P2 post is similar, but not the same as this issue. I think we need to keep this issue open.

david-szabo97 commented 3 years ago

1. It would be great to have a response from the REST API regarding the dotcom subdomain. The error message we get on the typo page would be ideal.

2. Another option is to just do something like this: image If the search results doesn't include a dotcom domain then show something like this.

3. Or as a third option how about calling the onlydotcom suggestion? That would send back a suggestion that's valid. For example 23332321 would return 23332321online.wordpress.com

https://public-api.wordpress.com/rest/v1.1/domains/suggestions?http_envelope=1&query=23332321&quantity=1&include_wordpressdotcom=true&include_dotblogsubdomain=false&only_wordpressdotcom=true&tld_weight_overrides=&vendor=dot&vertical=

If someone isn't getting suggestions because of being flagged as spammer then we could use option 2. In other case we can go with option 3

klimeryk commented 3 years ago

Related issue: https://github.com/Automattic/wp-calypso/issues/40967 (closed in favour of this one).

hambai commented 3 years ago

Okay - I have a backend fix for numeric search in D57568-code and for the other case in D57588-code.

razvanpapadopol commented 3 years ago

@hambai, @davipontesblog, can we close this one now?

davipontesblog commented 3 years ago

Thanks for the ping @razvanpapadopol. I have moved the issue to the HE triaging board so we can test if this is still happening.