berndtl

I started an issue on GitHub, but the developers don’t seem to grasp the concept of inline-javascript vs using files that can be defer loaded.

So no movement so far :-/

The quick fix is to find a defer loader plugin which is inactive on the admin pages – Or to rewrite the defer loader you have in functions.php to have an !is_admin() condition set when being loaded.

• This reply was modified 6 years, 3 months ago by berndtl.

As @ropezg points out, that line is the error.

I wrote a little bit about how to fix it here:

https://www.ads-software.com/support/topic/blank-editor-screen-fix-8-0/

But the jist is that Yoast did some “worst practice” javascript coding, which breaks when you speed optimization on your javascript loading. I mean who would ever have that on a SEO optimized site /s

@jerparx.

I posted a solution to a problem that many people have, and you can’t even be bothered to pas it along to the Developers? I know that you’re just a community manager, but your reply really reflects poorly on Yoast as a company.

Mazedul, your programmers got lazy and did this:

wp_add_inline_script( self::PREFIX . ‘lodash’, ‘window.lodash = _.noConflict();’, ‘after’ );

on line 221 in admin/class-admin-asset-manager.php

Rewrite it to have it load properly from a javascript file with dependencies set as they should be.

Temporary fix: find all javascript defer loading mechanism on your site and disable them, or rewrite them to not run on the admin screens.
Most likely it’s because you are defer loading javascript through a simple function in functions.php.

Same here – editor only works with Yoast Disabled. Only “vanilla” type plugins on the site.

Issue seems to be that lodash or underscore.js isn’t loading:

The line,
`window.lodash = _.noConflict();

Throws an “Uncaught ReferenceError: _ is not defined” error.