• Resolved simoptim

    (@simoptim)


    Ive upgraded to the newest YOAST SEO version.
    In my backend, i recieve an error if the YOAST is activated => my builder (Divi Builder) is not loading anymore.
    Ive checked the Console and its an error with YOAST: https://cl.ly/3T0f1E1Z1u3Q

Viewing 4 replies - 1 through 4 (of 4 total)
  • Samme issue here.

    Backend of my WPBakery Page Builder is not loading anymore, too! ??

    MariusG

    (@marius_codeinwp)

    Hey @simoptim,

    Please let us know if you are also using the latest version too, so that we may try to replicate this issue on our side.

    In addition, please check if the issue persists when only Divi and Yoast SEO are active.

    @toto1988, please create a new issue as the problem is related to a different plugin in your case. Additionally, please check if increasing the maximum memory limit fixes this issue, as it’s a common reason for the editor not to load.

    Hello,

    same thing happens to me as well, since about 7 days ago (Divi 3.10.1, Yoast SEO Premium 7.8). Support at Yoast is not very responsive/supportive on the matter, trying to blame other plugins etc.

    I did what they asked (check backend without any other plugin active, send JS-error report generated with console, that BTW names the SEO-plugin a culprit). I haven’t heard from them since then.

    Divi support says they see the problem and are working on it as well.
    https://www.elegantthemes.com/forum/viewtopic.php?f=187&t=885664&p=4868203#p4868203

    Here’s a screenshot of the console error log:
    https://prnt.sc/k7tus9

    Let’s keep our fingers crossed then…

    • This reply was modified 6 years, 8 months ago by Oligraph.
    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    @midway88 We apologize for any inconvenience. Since you are running Yoast SEO Premium, you can directly send us an email at [email protected] and we’d be happy to investigate this issue further on your site.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error in the backend after upgrade to 7.8’ is closed to new replies.