Conflict with Gutenberg?

Getting the following error when using Hummingbird on a WP 5.1.1 Gutenberg enabled site when I try to add a new post. I get a blank white screen that says “The editor has encountered an unexpected error.” with 3 buttons, “Attempt Recovery”, “Copy Post Text”, and “Copy Error”.

cb@wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:12:450

p@wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:13:214

mc@wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:73:135

Cf/<@wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:82:391

P@wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:84:497

ph@t/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:97:465

eg@/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:125:307

fg@/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:126:168

wc@/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:138:237

gg@/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:135:160

Se@/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:40:45

  • Jason
    • New Recruit

    Here’s the output from console with script debug enabled;

    Warning: Unsafe lifecycle methods were found within a strict-mode tree:
    in StrictMode (created by Editor)
    in Editor (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithSelect(Editor)

    componentWillUpdate: Please update the following components to use componentDidUpdate instead: FillComponent

    Learn more about this warning here:
    https://fb.me/react-strict-mode-warnings react-dom.js:500:32
    warningWithoutStack http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:500
    flushPendingUnsafeLifecycleWarnings http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:10441
    flushPendingUnsafeLifecycleWarnings http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:10418
    commitAllLifeCycles http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:17373
    callCallback http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:143
    invokeGuardedCallbackDev http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:193
    invokeGuardedCallback http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:250
    commitRoot http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:17582
    completeRoot http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:19036
    performWorkOnRoot http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:18965
    performWork http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:18873
    performSyncWork http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:18847
    requestWork http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:18716
    scheduleWork http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:18525
    enqueueSetState http://produce.vagrant/wp-includes/js/dist/vendor/react-dom.js?ver=16.6.3:12437
    setState http://produce.vagrant/wp-includes/js/dist/vendor/react.js?ver=16.6.3:460
    onStoreChange http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:1839
    globalListener http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:1243
    globalListener http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:1242
    subscribe http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:640
    dispatch http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:2374
    promiseMiddleware http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:514
    createResolversCacheMiddleware http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:569
    createMiddleware Redux
    dispatch http://produce.vagrant/wp-includes/js/dist/data.js?ver=4.2.1:2759
    Redux 4
    run http://produce.vagrant/wp-includes/js/dist/vendor/wp-polyfill.js?ver=7.0.0:4399
    notify http://produce.vagrant/wp-includes/js/dist/vendor/wp-polyfill.js?ver=7.0.0:4416
    flush http://produce.vagrant/wp-includes/js/dist/vendor/wp-polyfill.js?ver=7.0.0:1501
    The above error occurred in the <render> component:
    in render (created by PluginArea)
    in div (created by PluginArea)
    in PluginArea (created by Layout)
    in div (created by Layout)
    in Layout (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithViewportMatch(Layout) (created by NavigateRegions(WithViewportMatch(Layout)))
    in div (created by NavigateRegions(WithViewportMatch(Layout)))
    in NavigateRegions(WithViewportMatch(Layout)) (created by ComponentWithDispatch)
    in ComponentWithDispatch (created by Context.Consumer)
    in WithDispatch(NavigateRegions(WithViewportMatch(Layout))) (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithSelect(WithDispatch(NavigateRegions(WithViewportMatch(Layout)))) (created by Editor)
    in ErrorBoundary (created by Editor)
    in SlotFillProvider (created by EditorProvider)
    in div (created by DropZoneProvider)
    in DropZoneProvider (created by EditorProvider)
    in EditorProvider (created by ComponentWithDispatch)
    in ComponentWithDispatch (created by Context.Consumer)
    in WithDispatch(EditorProvider) (created by Editor)
    in StrictMode (created by Editor)
    in Editor (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithSelect(Editor)

    React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary. react-dom.js:15873:13
    Error: Objects are not valid as a React child (found: object with keys {type, key, ref, _owner, _context, _store}). If you meant to render a collection of children, use an array instead.
    in render (created by PluginArea)
    in div (created by PluginArea)
    in PluginArea (created by Layout)
    in div (created by Layout)
    in Layout (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithViewportMatch(Layout) (created by NavigateRegions(WithViewportMatch(Layout)))
    in div (created by NavigateRegions(WithViewportMatch(Layout)))
    in NavigateRegions(WithViewportMatch(Layout)) (created by ComponentWithDispatch)
    in ComponentWithDispatch (created by Context.Consumer)
    in WithDispatch(NavigateRegions(WithViewportMatch(Layout))) (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithSelect(WithDispatch(NavigateRegions(WithViewportMatch(Layout)))) (created by Editor)
    in ErrorBoundary (created by Editor)
    in SlotFillProvider (created by EditorProvider)
    in div (created by DropZoneProvider)
    in DropZoneProvider (created by EditorProvider)
    in EditorProvider (created by ComponentWithDispatch)
    in ComponentWithDispatch (created by Context.Consumer)
    in WithDispatch(EditorProvider) (created by Editor)
    in StrictMode (created by Editor)
    in Editor (created by ComponentWithSelect)
    in ComponentWithSelect (created by Context.Consumer)
    in WithSelect(Editor)

  • Nithin
    • Support Wizard

    Hi Jason,

    I installed a fresh new install of WordPress 5.1.1, and tested Hummingbird v 2.0.1. I’m not able to replicate any issues with editing or adding posts via Gutenberg.

    Also tested with the latest version of WordPress 5.2.2, and it seems to load fine. The above console errors don’t give much info regarding the issue specific to Hummingbird.

    Could you please grant support staff access so that we could give a closer look. You can grant access from WPMU DEV > Support > Support Access > Grant Access, or check this manual: https://premium.wpmudev.org/docs/getting-started/getting-support/#chapter-5

    Please let us know once you enable access so that we could get this sorted. Have a nice day. :slight_smile:

    Kind Regards,

    Nithin

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.