Open thingalon opened 7 months ago
Hi @thingalon, I had a user with a private atomic site. They wanted to add users as viewers. When viewers accept invites, they see the User cannot access this private blog
. But soon after that, they are added as viewers to the site. I could replicate it on the user's site and my test site.
This is confusing for the users. They want to add 100+ viewers and it won't be a good experience for them if this error appears. I wanted to mention it here in case it helps with the case.
More context in 7782603-zd-a8c
Support References
This comment is automatically generated. Please do not edit it.
Here are the findings of my testing:
So, there is an error message being reported even though the user is able to register.
@vinnykaur, @masperber - this ticket is on the Jetpack board and is focused on API errors Jetpack Boost users are seeing when interacting with the plugin on a private WoA site. It doesn't really relate to core WordPress flows like user management in WoA.
We're not the right place to be tracking this issue, and I'm afraid it will get lost here and won't get the attention it deserves. It needs to be reported in a WPCOM/WoA issue tracker.
Thanks! There is another bug report for the WoA private sites here: https://github.com/Automattic/wp-calypso/issues/66547
Thanks for pointing us in the right direction.
This issue has been marked as stale. This happened because:
No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.
AFAIK we haven't done anything in this direction, so this is still relevant.
When a WoA site is marked as "Private", some Boost features no longer work. This includes Cloud CSS and Speed Scores, for different reasons:
User cannot access this private blog
. p1706715644352229/1706626329.415869-slack-C01U2KGS2PQThis is a bit messy. It's reasonable that some features do not work on a site that is not publicly accessible. I think we should make Private sites on WoA behave like offline sites, so that users get a clean, understandable experience.