Updated to 2.6.0.3 breaks my site

Updated to 2.6.0.3 breaks my site => mee to…

I had to restore a backup of my site and block automatic updates

Same for me, the site is broken after the update. I also restored a backup.
I use WP 6.0.3, WP Rocket, VamTam Builder.

• This reply was modified 2 years, 4 months ago by dmelendo.

Unfortunatly Vantam themes are not compatibale with version 2.6 and they refused to fix the issue or add support.

Lucky for you though I did fix the issue late late night and we will release a fix later today with the following code added that stops the vantam fatal error.

for now add this to your child theme functions.php

add_action( 'after_setup_theme', function() {
	add_filter( 'vamtam_less_vars', function( $vars ) {
		if ( isset( $vars['beaver-global'] ) ) {
			foreach( $vars['beaver-global'] as $k => $var ) {
				if ( is_object( $var ) || is_array( $var ) ) {
					unset( $vars['beaver-global'][$k] );
				}
			}
		}
		return $vars;
	});
});

We are facing a similar issue with beaver builder 2.6.0.3.
Do we have any fix for this? or just have to wait for the update of the beaver builder plugin?

@pratikshelke see the comment right above yours for a workaround.

@pratikshelke You can add the fix mentioned by @pross above or wait until we push out an update. I would also advise you to get in touch with VamTam themes as this would be best fixed on their end. Our fix is more of a bandaid for the problem.

If they are going to fix it contrary to what we’ve been told, then we’d wait on pushing out our update.

• This reply was modified 2 years, 4 months ago by Jamie.

thank you, its working now.

Thanks for this helpful thread – I’m glad that Vantam did push out an update which fixed things for me too, but just wanted to shout out to the helpful support from you guys!

> I’m glad that Vantam did push out an update which fixed things for me too

Wait, they fixed it?

They def released an update today and with it installed I could update BB Lite without a fatal error so I believe so (even tho the Changelog did not specifically call this issue out).

Well thanks for letting us know, that means we dont have to release an update now!