gullwingio

We also just discovered if anyone else has this issue, WP 6.2 running on VIP you can also add this:

client-mu-plugins/plugin-loader.php

if ( is_admin() ) {
    remove_action( 'init', 'js_concat_init' );
}

This also fixes it for that version

My comment above has now proven to be wrong, it was actually the WordPress version and this plugin. When we upgraded WordPress VIP to 6.3 we could remove this code and the plugin works fine, with 6.2 you need &concat_js=no in the URL else you get this error.

• This reply was modified 1 year, 5 months ago by gullwingio.

Just for anyone might might run into this, we had to do the following:

In your client-mu-plugins/vip-gutenberg-config.php file:

add_filter( 'js_do_concat', 'my_vip_js_concat_filter', 999, 2 );
function my_vip_js_concat_filter( $do_concat, $handle ) {
    if ( is_admin()) {
        return false;
    }
    return $do_concat;
 }

Thank you for the response.

So yeah the editor doesn’t load, you just get this error unless you add the ‘&concat_js=no’?

I’m trying think off anything else interesting I can give you. Local works fine but thats because it has ‘&concat_js=no’?on by default. As soon as we deploy to our development environment we get this issue.

Without concat_js, we can see in the console jquery not being defined, which is the only thing we have to go on. We are unsure of the VIP build steps, but we guess it’s doing something because we noticed that it stripped out the?javascript:?part from?<a href='javascript:void()'...?so assuming the build step has some kind of security sanitation or something that isn’t present locally.

The only other thing we can think is its a WIPVIP instance / build where we raised a ticket as well.