• Resolved Kevin Pfeifer

    (@beardcat)


    Dear Yoast Community!

    Since the Yoast 12.0 Update I get the following JS error when opening a post in backend.

    analysis-1200.min.js:21 Yoast SEO and readability analysis: An error occurred during the building of the tree structure used for some assessments.
    
     TypeError: Cannot read property 'length' of undefined
        at a.value (analysis-1200.min.js:21)
        at a.value (analysis-1200.min.js:21)
        at a._insertCharacters (analysis-1200.min.js:21)
        at Object.Wa [as CHARACTER_TOKEN] (analysis-1200.min.js:21)
        at a.value (analysis-1200.min.js:21)
        at a._processToken (analysis-1200.min.js:21)
        at a.value (analysis-1200.min.js:21)
        at a.value (analysis-1200.min.js:21)
        at a._runParsingLoop (analysis-1200.min.js:21)
        at a.value (analysis-1200.min.js:21)

    See: https://i.pfiff.me/Yoast-SEO-Error.png

    Therefore the JS execution has been stopped and Gutenberg is broken.

    When I deactivate Yoast SEO everything works again.

    Any Ideas?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Kevin Pfeifer

    (@beardcat)

    Im sorry but somehow my problem has solved itself.

    Probably it was my caching Plugin “Autoptimize” which could have caused the problem above but I can’t reproduce my problem any more even though i tried clearing all the caches before submitting this issue.

    I can edit all my posts and Yoast doesn’t overlay Gutenberg any more (like in the screenshot above)

    taking into account Autoptimize doesn’t optimize wp-admin screens (as confirmed by the filenames in the JS error), this is very unlikely to be due to AO. however, if you encounter this again feel free to ping me and I’ll be happy to provide feedback where needed ??

    have a great weekend,
    frank

    Thread Starter Kevin Pfeifer

    (@beardcat)

    Unfortunately I “rediscovery” the problem.

    See this screenshot: https://i.pfiff.me/Yoast-SEO-Gutenberg-overlays-content.png

    The strange thing here is, that i don’t get the mentioned JS error as described above in my initial post any more.

    Also I have cleared the Autoptimize cache again AND deactivated the Autoptimze Plugin and the problem still persists. Therefore its definitely not the Plugin, but thanks to “Optimizing Matters” for the quick reply ??

    Back to the problem: I tried some more plugin disabling and discovered, that it is definitely a Gutenberg problem in itself. Both Yoast SEO and the Supersozializer Plugin installed alone did overlay the Gutenberg content, therefore I will create an issue for Gutenberg and it is definitely NOT a problem with Yoast.

    Its still strange to me, that in the beginning disabling Yoast fixed my problem, but this doesn’t happen any more.

    Here some more Screenshots to illustrate my current state:
    https://i.pfiff.me/installed_plugins.png
    https://i.pfiff.me/Yoast-SEO-Gutenberg-overlays-content2.png

    Thread Starter Kevin Pfeifer

    (@beardcat)

    OK, more Information!

    There is already an open Issue for the WordPress Gutenberg Github Project.

    See here: https://github.com/WordPress/gutenberg/issues/13503

    I tried reproducing this problem in Safari and Firefox but I could not do it.

    Therefore I completely removed all the caches I had in my Chrome but it still persists, therefore it has to do something with the current Chrome 77.0.3865.75 (MacOS) Version since I could not reproduce the problem with the Chrome 76 Version on my Windows machine.
    But after I updated the Windows Chrome to 77 the problem is there… well done Google…

    Guess it’s this one; Metaboxes overlap Gutenberg in Chrome 77 #17406, workarounds are included.

    Thread Starter Kevin Pfeifer

    (@beardcat)

    Uh nice, didn’t see that one. Thanks for that ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Yoast 12.0 breaks Gutenberg’ is closed to new replies.