block-options
block-options copied to clipboard
Cannot open a page preview with editorskit activated
Support
Hello.
I am using the latest version of editorskit (1.33). When I try to open a page preview (both from a draft page/post or a published page/post), the page cannot be open (refused to connect).
If I deactivate Editorskit and so I have the deafult Gutenberg, the preview works normally….
Please check it.
BR.
Details
- Support Author: gemont
- Support Link: https://wordpress.org/support/topic/cannot-open-a-page-preview-with-editorskit-activated/
- Latest Activity: 1 minute ago
- Spinup Sandbox Site: https://tastewp.com/new/?pre-installed-plugin-slug=block-options
Note: This support issue is created automatically via GitHub action.
Video Link : https://share.getcloudapp.com/Wnuko21Z
Having the same issue. The error is:
TypeError: Cannot destructure property 'patternCategories' of '(0 , m.useSelect)(...)' as it is undefined. at Pu (http://.test/app/plugins/gutenberg/build/block-editor/index.min.js?ver=6fc2163e8677ee351c15e4aa9e7f68ae:12:6542) at vd (http://.test/app/plugins/gutenberg/build/block-editor/index.min.js?ver=6fc2163e8677ee351c15e4aa9e7f68ae:27:2770) at renderWithHooks (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:15015:20) at mountIndeterminateComponent (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:17841:15) at beginWork (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:19079:18) at HTMLUnknownElement.callCallback (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:3942:16) at Object.invokeGuardedCallbackDev (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:3991:18) at invokeGuardedCallback (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:4053:33) at beginWork$1 (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:23994:9) at performUnitOfWork (http://.test/app/plugins/gutenberg/vendor/react-dom.860550b4.js:22806:14)
@lukasz-gorski Thanks, we are looking into this. 👍
@ZafarKamal123 There are more users who added comments for this issue with some more details in the WP Org forum, do check that out as well.