Opened 23 months ago
Last modified 23 months ago
#56953 new defect (bug)
TypeError: Cannot destructure property 'themeSupportsLayout' of '(0 , p.useSelect)(...)' as it is undefined
Reported by: | pigot4 | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 6.1 |
Component: | Editor | Keywords: | reporter-feedback |
Focuses: | Cc: |
Description
Hi
this morning with update of WP to 6.1 have a lot of problems. I tried to deactive all plugins and I think that is an error of Core.
TypeError: Cannot destructure property 'themeSupportsLayout' of '(0 , p.useSelect)(...)' as it is undefined.
at https://domain.com/wp-includes/js/dist/block-editor.min.js?ver=d39738cb7c1202964677:26:193469
at ct (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:43430)
at os (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:111136)
at Ur (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77643)
at Ir (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77571)
at Dr (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77434)
at Pr (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:74429)
at https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:30173
at unstable_runWithPriority (https://domain.com/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:9:7431)
at xn (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:29950)
I tried to reinstall WP but the link is on 404:
https://downloads.wordpress.org/release/it_IT/wordpress-6.1.zip
I've bug on editor of themes, on create new content and on front-end
Please fix the problem
Attachments (3)
Change History (4)
#1
@
23 months ago
- Component changed from General to Editor
- Keywords reporter-feedback added
- Severity changed from blocker to normal
Hi @pigot4,
Welcome to trac! Could you try setting the SCRIPT_DEBUG
constant and then copy the error again? That should give a bit of an easier error message to understand.
Update in 404