• Resolved welje

    (@welje)


    Hi,

    When I use the Clasic Editor after installing Gutenberg, the Yoast fields no longer work in post page.

    Error :

    wp-seo-replacevar-plugin-790.min.js?ver=7.9:1 Uncaught ReferenceError: yoastWebpackJsonp is not defined at wp-seo-replacevar-plugin-790.min.js?ver=7.9:1

    • This topic was modified 6 years, 4 months ago by welje.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Jerlyn

    (@jerparx)

    Unfortunately, we’re unable to reproduce the issue in our test environment. Can you please provide a workflow on how we can replicate the issue? Currently, we have the following setup:
    -WordPress 4.9.8
    -Yoast SEO 7.9
    -Gutenberg 3.4.0
    -Theme: Twenty Seventeen 1.7

    Thread Starter welje

    (@welje)

    Same, with the Classic editor plugin activate.

    @welje I have had sever issues with yoast free that I have been trying to troubleshoot on my own.
    Last nights( by last night I mean this am still havent slept ) break thru is this. Yoast free bread crumbs on is faulty with some part of my set up. Host? I am on apache http1.1 NGINX – I have not done the recommended yoast rewrites. Theme – I am using the Elementor Hello theme with a custom child theme that I wrote ( this could be the flaw ) Elementor pro with the Yoast Bread crumb saved as a global template. My issue was unable to save any page in elementor pro due to none stop 500 server error.

    The fix was deactivating Yoast free. Which sucks cause I love yoast and really want to use it, in 2015 it helped me organic rank all my clients.

    Your posted issue with yoast being unable to analysis the words with gutenberg has been reported a few weeks back with the elementor pro customer support. It affects way more then just the gutenberg editor.

    Yoast has been tragically broken for a while now and we all have been waiting on Gutenberg release so they can say yes this it is now time to devote to patch. It does not make sense as a company to patch before release. Look at how many Nvidea drivers they push in beta to find a flaw in the game they beta pushed for. I support yoast waiting for Gutenberg release to patch.

    Some other things you might not have seen yet that we are all sitting on… Yoast no longer interfaces with any of the web master tools. It does not submit sitemaps to create robots.txt on my config. Unknown cause.

    My config is likely the cause due to my apache server and NGINX cache but… Most modern hosts have this so yoast needs to step up their game to support modern.

    The Interface with Web master tools is gonna be hard to fix cause Google changes something pushes it then changes it again in the timeit takes your cache to expire.
    I do not think Google has a deployment roadmap and they do everything live.

    The short of it, foe me was too loose the kick ass bread crumbs and deactivate yoast free and reindex with search engines manually( for all clients )

    I would like to think yoast is aware of all these issues and is just making a roadmap on a white board in an office while the coders nod and drink monsters.

    FYI github has a RC1 Yoast candidate 8.0 that has a newer JS of the file your having issues with but is showing to be 11 commits behind trunk?

    I kinds think yoast is having issues with MS github takeover and pushes to svn…

    the trunk is ahead of SVN file wise and the 8.0 branch was partial merged with 7.9x this either means the hired an intern or… above statement is true.

    if ya feel like being a test monkey… go grab it.
    https://github.com/Yoast/wordpress-seo/tree/release/8.0

    @jerparx tagged ya to notify ya to condense these error posts into this one or else your gonna have 1000s of tickets.

    You likely have a Git hub versioning push to svn issue.
    Your trunk on git hub does not match svn. Also your RC1 branch was partial merged with 7.9X which means your internally running code that is not available to the worls thru the WordPress update feature.

    Same issue here. When I use the Clasic Editor after installing Gutenberg, the Yoast fields no longer work in post page.

    Thread Starter welje

    (@welje)

    Idem with Yaost 7.9.1 …

    MariusG

    (@marius_codeinwp)

    Hey guys,

    Thank you for reporting this issue, we’re sorry for the troubles. Upon further investigation, we found that this issue happens when both Gutenberg and Classic Editor plugins are active.

    We have opened a GitHub issue and sent it to our development team, they will provide a solution as soon as possible. In the meantime, you can follow the progress or let us know if you have any other information here.

    Plugin Support Michael Ti?a

    (@mikes41720)

    Please update to the latest version v8.0 of Yoast SEO for WordPress and this should be resolved accordingly.

    Setting to resolved.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘4.9.8 and Gutenberg’ is closed to new replies.