-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Widgets editor] Replace the "technical" error notice a more user-friendly one #33165
Conversation
Size Change: +80 B (0%) Total Size: 1.05 MB
ℹ️ View Unchanged
|
I would phrase as "Some blocks" instead of "The following blocks". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and merged, happy to update the phrasing if needed. |
This phrasing works well! Just to clarify, if multiple blocks are affected, will the wording slightly change ("were affected")? |
For now we'll show multiple notices. I'd like to have that all "flattened" to just a single message eventually, but it is not a case ATM. |
Description
I believe that, besides its technical aspects, Trac #53437 is largely a communication problem. We need to somehow tell the user that the error happened, but saying wp.editor.initialize is not a function or dropping any other error message isn't very helpful to the user.
We could just disable the affected widgets, but we still need to communicate it, it’s just the wording would be more like "The following blocks (...) have been disabled".
Two things this PR is missing are:
Blocks 'text' and 'plugin/cool-editor' were affected...
) –Before – a cryptic message and no stack trace:
After – an informative message + a relevant stack trace logged in the console:
How has this been tested?
Types of changes
Bug fix