-
Notifications
You must be signed in to change notification settings - Fork 8
Block Editor: Improve Detection #938
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
Conversation
…ge/Post/CPT, to determine how to display an error message
WordPress Playground🚀 Your PR has been built and is ready for testing in WordPress Playground! |
…into improve-divi-tests
noelherrick
left a comment
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.
This could be a helper with a test so that readers can easily understand what you're trying to do by adding an explanatory name, and since wp.editPost doesn't seem to be an API for checking what you're checking, so a bit more subject to change, it would be nice to just update it one place.
WordPress Playground🚀 Your PR has been built and is ready for testing in WordPress Playground! |
Block Editor: Add `convertKitGutenbergEnabled` helper
Improve Divi Tests
Summary
When testing for WordPress 6.9 beta, two issues found:
Manually refreshing resources with an invalid/expired access token would result in no error message displaying

A JS error in the browser console.

This PR resolves by:
wp.editPost(only defined if the block editor is active) instead ofwp.blockEditor(which in WordPress 6.9 beta is always defined, regardless of whether the block editor or Classic Editor is used)Changes are in this PR vs. the 6.9 beta PR, to make sure no breaking changes are introduced for those still on the current public version of WordPress 6.8
Testing
Existing tests pass.
Checklist