-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Gutenberg NUX welcome modal: hide per user, not per site-per-user #40040
Comments
Another related thought: If hidden after a first view (any site, same user) — is there an easy way to relaunch it? Self-help where someone wants to watch the tutorial again. Rather than interrupting the editing flow (blocking a user) — how might we make it available but non-blocking? |
Good question! It's available on the three dots sidebar right now, tho might move to another place in future: WordPress/gutenberg#19499 |
It should only show once per user—most folks have 1 site. I think Automatticians are unique cases. We can set a rules: Since we still have duplicate sites issue, this is something we should consider after we've fixed that bug (unless it's a minority of folks who land on the duplicate site issue) |
This was solved in #39846. It should now only appear one time per user. If you dismiss it again, you will not see it any again. This change probably wasn't deployed at the time the issue was reported here! The FSE update containing the change had to be rolled back, but it should be live now. Please let us know if you continue seeing the issue. Edit: to clarify, this is live for Simple sites at the moment. Atomic sites have the code, but it is disabled due to an incompatibility issue with core WordPress (so we have to deploy code which checks for compatibility.) This is the bug that caused the outage earlier this week. |
working on the Atomic fix here: #40081 |
The welcome guide was enabled for .com in #38511
Via @lancewillett at #38511 (comment):
@olaolusoga @joanrho @dubielzyk thoughts on this?
The text was updated successfully, but these errors were encountered: