Closed TPilgs closed 2 years ago
Been able to replicate when SU'd, but unable to replicate on my tests. A user is attempting to select Add New Site from their switch sites menu and it only loads a blue page.
This link appears: https://wordpress.com/start/domains?ref=calypso-selector&source=my-home&siteSlug=null
Removing the &siteSlug=null fixes the issues as a workaround.
It should bring up the create new site workflow.
It shows a blank page, but it's intermittent depending on who has tried it.
{5655440}-zen is the one that brought the issue up and the one that, if SU'd, doesn't work for me or a few others.
Slack thread here:
{p1666629795505489}-slack-{wpcomsupport}
Simple, Atomic
N/A
We've tried on updated versions of Chrome and Firefox.
Intermittent
Most (> 50%)
Yes, easy to implement
Removing the &siteSlug=null fixes the issues as a workaround, but the user(s) likely won't know this unless they reach out to us.
Support References
This comment is automatically generated. Please do not edit it.
Quick summary
Been able to replicate when SU'd, but unable to replicate on my tests. A user is attempting to select Add New Site from their switch sites menu and it only loads a blue page.
This link appears: https://wordpress.com/start/domains?ref=calypso-selector&source=my-home&siteSlug=null
Removing the &siteSlug=null fixes the issues as a workaround.
Steps to reproduce
What you expected to happen
It should bring up the create new site workflow.
What actually happened
It shows a blank page, but it's intermittent depending on who has tried it.
Context
{5655440}-zen is the one that brought the issue up and the one that, if SU'd, doesn't work for me or a few others.
Slack thread here:
{p1666629795505489}-slack-{wpcomsupport}
Platform (Simple, Atomic, or both?)
Simple, Atomic
Theme-specific issue?
N/A
Browser, operating system and other notes
We've tried on updated versions of Chrome and Firefox.
Reproducibility
Intermittent
Severity
Most (> 50%)
Available workarounds?
Yes, easy to implement
Workaround details
Removing the &siteSlug=null fixes the issues as a workaround, but the user(s) likely won't know this unless they reach out to us.