Closed miguelpeixe closed 2 years ago
Thank you for catching that! I realize now that we should have a better strategy for disabling the use of the block instead of removing its registration entirely.
07a223ebe4c3fd7040d69ed32c561c5da6c0ac93 displays an error message on block edit and modifies the render callback.
:tada: This PR is included in version 0.6.1-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 0.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
This PR disables the registration of the SCAIP block if the sidebars are disabled. SCAIP should assume that disabling sidebars means there is another method in place for handling how the ads are registered and rendered. There's no need for it to have its own block in such a case since it can duplicate and potentially conflict with the feature that has taken over.
To fix the integration with the block-based widget editor introduced by WordPress 5.8, this PR also removes the
wp-editor
dependency from the block editor JS. Declaring its dependency does not affect the block behavior.How to test
Block-based widgets
Disabled SCAIP block
Note: If you are running an instance with Jetpack enabled and connected, you might still see the warning due to https://github.com/Automattic/jetpack/issues/20357