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

Primary domain change warning for .home.blog sites #60291

Open
marutim opened this issue Jan 20, 2022 · 2 comments
Open

Primary domain change warning for .home.blog sites #60291

marutim opened this issue Jan 20, 2022 · 2 comments
Labels
[Pri] Normal Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report

Comments

@marutim
Copy link

marutim commented Jan 20, 2022

Quick summary

If users with a free .home.blog default domain on a paid plan attempt to cancel the plan, they’ll see a warning message saying the address would be redirected to the .wordpress.com subdomain. However, that’s not the case.

Steps to reproduce

  • Access a site with a paid plan and a free .home.blog subdomain.
  • Go to https://wordpress.com/me/purchases, click on the plan, and click the cancellation link at the bottom of the page
  • You will see an error message saying something like this: “When you downgrade your plan, [sitename].home.blog will immediately start forwarding to [sitename].wordpress.com. [sitename].wordpress.com will be the address that people see when they visit your site. Would you still like to downgrade your plan?
  • If you actually cancel the plan and downgrade the site to the free plan, the .home.blog address would still remain to be the primary domain for the site.

Screenshot:

image

What you expected to happen

I expect the warning message to display the correct domain to avoid any confusion.

What actually happened

The warning message says the address would be redirected to the .wordpress.com subdomain. That should rather say the address would be redirected to .home.blog subdomain

Context

No response

Simple, Atomic or both?

No response

Theme-specific issue?

No response

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

No response

Available workarounds?

No response

Workaround details

No response

@marutim marutim added [Type] Bug User Report This issue was created following a WordPress customer report labels Jan 20, 2022
@marutim marutim added this to Needs triage in HE Triaging Board (new bugs) via automation Jan 20, 2022
@Greatdane
Copy link

Can reproduce;

Screen.Capture.on.2022-02-07.at.15-11-44.mov

In my case, the *.wordpress.com domain for my site was already taken, which is confusing.

@Greatdane Greatdane moved this from Needs triage to Triaged in HE Triaging Board (new bugs) Feb 7, 2022
@Greatdane Greatdane added Triaged To be used when issues have been triaged. [Pri] Normal labels Feb 7, 2022
@cometgrrl cometgrrl moved this from Triaged to Prioritized - Bugs in HE Triaging Board (new bugs) Feb 7, 2022
@obenland
Copy link
Member

Are there any subdomains other than .home.blog to which that would apply to as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Pri] Normal Triaged To be used when issues have been triaged. [Type] Bug User Report This issue was created following a WordPress customer report
Projects
Development

No branches or pull requests

3 participants