Sites: notices for suspended blogs are missing

[designsimply]

Raised by @apeatling and originally reported by @catrymer

Users need to be able to see when a site is suspended, and perform some limited actions on that site.

(original report: p4TIVU-5K-p2, also see: 555-gh-io)

[supernovia]

Suspended users currently have no indicator in Calypso of suspended status. Could we also swap the help form for a TOS form so they don't post appeals in the public forums?

[davidwatkis]

Adding some further context here at the behest of @rralian

As @supernovia mentioned on Jun 6, there is currently no messaging to users with suspended blogs that (a) the suspension is the cause of the restricted functionality and (b) they need to contact the Terms of Service team to resolve the issue.

The result is that a user whose blog is suspended will have no indication what steps they should take and could mistake the suspension as a problem with the platform. And because there is no clear path to contact support staff, we're unable to determine exactly what problems users might be experiencing due to this issue nor are we able to help them find a solution.

[designsimply]

For reference, here is how the current notice looks in wp-admin

Here is a proposed design for a new notice /ht @rickybanister

[rralian]

@dllh I think this would most clearly fall under your team. Not that it falls into anyone's bailiwick perfectly. Is this something your team could tackle?

[rickybanister]

That design is pretty old at this point and we've made some advances in showing notices. When someone picks up this work I'd be happy to help wrangle an up-to-date design. Probably using a globalNotice with the ellipsis menu for the various options. It would be non-dismissable.

The options listed on the right side would go into the ellipsis menu with contacting support being the primary. Shortening the message would also help—reading a lot of white text on red is sub-optimal.

[catscheer]

We shortened the message quite a bit as part of the hackday project @jmdodd worked on to at least get a suspension message into notifications. You can see the shorter version, and how the notification looks, at:

https://cloudup.com/cBCizF8WO6W

[rickybanister]

I knew I remembered something happening here :)

Can't users still attempt to perform some actions within Calypso, which might be confusing if they only see an error after the fact?

Could we disable most action buttons or display a modal popover on all pages other than export?

[dllh]

My team is the team that would most likely pick this up, but it's not something I have bandwidth for immediately or in the medium term without pushing off some current work and work we've explicitly been asked to pick up in other areas of the product. I'll add to the project trello board for the future, though.

[codebykat]

Potential API patch in the linked repo.

[lancewillett]

Moving to normal priority based on @dllh's comment on available time to work on it.

[lancewillett]

Bug scrub note: this is still in-progress on the API side (marked High Priority).

[stale]

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏

[davidwatkis]

We definitely want this issue to remain open as it has not yet been resolved. The most recent overview of the suspension experience in Calypso which includes the absence of these notifications may be found here:

Internal reference: p4TIVU-7EB-p2

[cathymcbride]

@supernovia do you know if this still repros?

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[supernovia]

Weird, this mention just showed up 😬
I am fairly certain this is still an issue, but someone who works more with suspended sites would know better. I'll ping the right folks.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[worldomonation]

👋 Hey folks! Since this issue has been inactive for quite some time, KitKat has made the decision to close it.

• Internal reference, for more on this decision: pdqkMK-14B-p2

If you think this issue warrants another look, here are some next steps!

1. Report anew: A new report with more current details and steps to replicate may be the best way to renew attention on this issue. Feel free to refer back to this closed issue in your report!
2. Reopen: If you feel the issue still matches the context/history here, you can also reopen the issue and add fresh logs, screenshots and steps to reproduce.

Thanks for your involvement!

📌 ADDITIONAL NOTES