Support » Alpha/Beta/RC » Gutenberg giving error when creating new post

  • Resolved waterleat

    (@waterleat)


    If this is not in correct place please change it. I have been creating theme and plugin which works in 4.9.8. I want to see what is new in v5 and check compatibility etc.
    running on localhost – no problem with 2019 theme, however with my theme active the editor crashes when creating a new post. The first line of the error report reads:
    TypeError: Cannot read property ‘addQueryArgs’ of undefined
    Unfortunately I dont know where to find out what changes to theme handling have been done. Or is it because I use something in theme that is no longer compatible.
    Sorry I am very new at this.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Nichole Aber

    (@neverbenn)

    Since Gutenberg is not a part of core quite yet, your question may be best posted on the Gutenberg Plugin support forum to ensure the developers, contributors, and community involved with the project can find it there.

    Best of luck!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    @neverbenn – Gutenberg is included in WP 5.0 so this IS where people can start to ask for help.

    That said. This may be better to ask https://github.com/WordPress/gutenberg/issues/ or in the #core-editor room in slack, as it’s a Dev question with Alpha/Beta 🙁

    Nichole Aber

    (@neverbenn)

    My apologies! I retract my statement. Sorry if I muddied the waters.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    Totally understandable 😀

    The curious thing is that themes shouldn’t break with Gutenberg (Plugins, sure, but a theme?)

    waterleat

    (@waterleat)

    Thanks for the reply and hint that themes should be ok. I ahve tested several themes and found the one that does not work as expected. I note that:

    • tags and categories dropdowns not visible in editor sidebar
    • when autosave has started it does not seem to stop

    The error message prudeced is as follows:

        TypeError: Cannot read property 'addQueryArgs' of undefined
        at http://localhost/wp-includes/js/dist/edit-post.min.js?ver=5.0-beta2-43852:12:20580
        at t.value (http://localhost/wp-includes/js/dist/edit-post.min.js?ver=5.0-beta2-43852:12:20629)
        at t.value (http://localhost/wp-includes/js/dist/edit-post.min.js?ver=5.0-beta2-43852:12:20271)
        at Bc (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:145:188)
        at yc (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:136:182)
        at R (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:135:187)
        at eg (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:133:306)
        at ab (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:131:475)
        at Object.enqueueSetState (http://localhost/wp-includes/js/dist/vendor/react-dom.min.js?ver=5.0-beta2-43852:192:84)
        at r.setState (http://localhost/wp-includes/js/dist/vendor/react.min.js?ver=5.0-beta2-43852:20:392)

    The one thing that is different in this theme is that I incorporated tailwindcss. Perhaps v0.6.4 is the cause. I realise that latest version is v0.7.0 and I will have to rebuild and retest.
    I hope that we can find and resolve the conflicts.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    Have you been able to test again on the latest beta?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    Marking resolved as this was not reproducible and there has been no reply in a week.

    GDY

    (@grandy)

    I’ve create a fresh installation with twentynineteen and no plugins and got a similar error as soon as the editor opens. No matter if it is a existing page or post or a new one …

    TypeError: Cannot read property ‘core/paragraph’ of undefined

    GDY

    (@grandy)

    Also the copy post content button seem to do absolutely nothing when a error is triggered right away. Makes sense because the post content ist empty but why is this button then shown anyway …

    Jonathandejong

    (@jonathandejong)

    @grandy

    I just debugged this exact error for a client and reached the conclusion that is also posted here:
    https://github.com/WordPress/gutenberg/issues/14602

    So if you just clear your localstorage you should be good to go!

    GDY

    (@grandy)

    @jonathandejong that would be great. Thanks for answering i am going to try that tomorrow and let you know if that was the problem.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Gutenberg giving error when creating new post’ is closed to new replies.