Tracking Issue: sites stuck in a "Launch Site" state #91796
Labels
Customer Report
Issues or PRs that were reported via Happiness. Previously known as "Happiness Request".
[Feature Group] Signup & Site Onboarding
Tools for user registration and onboarding new users to the site.
[Feature Group] Site Settings & Tools
Settings and tools for managing and configuring your site.
[Feature] Site Settings
All other general site settings.
Needs triage
Ticket needs to be triaged
[Platform] Atomic
[Platform] Simple
[Pri] Low
[Product] WordPress.com
All features accessible on and related to WordPress.com.
[Type] Bug
Comments
|
8213241-zd-a8c @mrfoxtalbot please review this issue and confirm it portraits the feedback you shared correctly. |
|
Support References This comment is automatically generated. Please do not edit it.
|
Yes, this seems to be the same issue. I have stumbled into this 3-4 times in 5 months so it is probably happening fairly often. Setting the site as Coming Soon and then making it Public again fixed the problem every time. |
|
Another one in 8327906-zd-a8c The site was not showing thumbnails in the Media Library (related to #91136). I fixed it my setting the site as private and then as public again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quick summary
Sometimes, the site will get stuck in a state between unlaunched and launched, where the UI might treat it as a launched site in some context, but not on others. This affects customers with tasks like changing site privacy, editing/previewing content, and more. In general, HEs are able to launch sites for the customer, or clear the state by changing the privacy settings.
This issue is meant to track similar cases to determine a pattern/reproduction steps.
Steps to reproduce
No clear repro steps
What you expected to happen
The UI should indicate consistently if a site is launched/unlaunched and the site's features should also behave correctly based on that
What actually happened
Sites seem to get into a "limbo" state, and users are unable to use features like Preview correctly
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
Platform (Simple and/or Atomic)
Simple, Atomic
Logs or notes
No response
The text was updated successfully, but these errors were encountered: