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

[Bug]: Domain-only flow hangs at "preparing the domain for purchasing" #58101

Closed
hypest opened this issue Nov 16, 2021 · 1 comment
Closed

[Bug]: Domain-only flow hangs at "preparing the domain for purchasing" #58101

hypest opened this issue Nov 16, 2021 · 1 comment
Labels
Needs triage Ticket needs to be triaged [Type] Bug

Comments

@hypest
Copy link
Contributor

hypest commented Nov 16, 2021

Quick summary

Trying to buy a domain without a site ends up in the "Preparing domain for purchase" screen not going away.

Steps to reproduce

  1. Ensure not being logged in to WordPress.com
  2. Go to https://wordpress.com/domains/
  3. Search for a domain (example: iwantanewdomain)
  4. Select one of the options. I went with the recommended one (iwantanew.domains)
  5. Select "Just buy a domain"
  6. Hit the "Already have a WordPress.com account?" link at the bottom and log in to an existing non-A8c account
  7. Notice we land on the blue "We are preparing the domain for purchase…" screen but doesn't move on from there.
  8. Open the browser developer tools and notice 2 Uncaught TypeError: o.path is undefined errors in the console. Note: I don't get those errors on Chrome, but do get them on Firefox.

What you expected to happen

I was expecting to move past the "We are preparing the domain for purchase…" screen, going to payment information perhaps.

What actually happened

The flow stopped at "We are preparing the domain for purchase…".

Context

I was trying to see if I can buy a domain without buying a WPCOM plan. I found the domains page via Googling for "wordpress.com buy domain".

Browser

Mozilla Firefox

Simple/Atomic

No response

Other notes

No response

Reproducibility

Consistent

Severity

No response

Available workarounds?

No response

Workaround details

No response

@hypest hypest added [Type] Bug Needs triage Ticket needs to be triaged labels Nov 16, 2021
@jordesign
Copy link
Contributor

Closing this as the domains flow has changed since this report.

@jordesign jordesign closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs triage Ticket needs to be triaged [Type] Bug
Projects
None yet
Development

No branches or pull requests

2 participants