My Site Broke After Widgets Update

Do you have an old version of the plugin I can roll back to?

Sure, you can use a plugin like WP Rollback to roll back. Ideally, try to establish a working baseline. Clear WP Rocket, deactivate the plugin and then temporarily deactivate all non-SiteOrigin plugins. Is a working baseline available?

Thanks Andrew. I did rollback the driver and the site is working properly again. I also deactivated all plugins before rolling back the driver for the SiteOrigin Widgets Bundle and none of the deactivated plugins caused the interface to display properly. The latest Widgets Bundle version itself is the the problem. I have deactivated Auto-Update for the plugin.

Thanks. We’ll need to try and recreate your environment. Please let us know:

WP version. PHP version and is the server using Apache?

No worries. WP Current version: 6.2 Last checked on May 4, 2023 at 9:27 am CDT.

PHP v. 8.1

I do believe server is using Apache (InMotion Hosting VPS server with 8 cores and 8GB memory) and also using NGNIX for caching. I did clear the NGNIX cache several times yesterday and that did not resolve the issues I had.

Apache Version 2.4.57
MySQL Version 10.3.38-MariaDB
Architecture x86_64
Operating System linux

Thanks. I don’t see anything that we haven’t tested with in the list. Does InMotion offer the ability to easily spin up a testing/staging site?

I can’t currently reach this, but can you try staging.usaindustries.com and see if the site comes up for you?

Thanks, I can reach the URL in question. Please, try editing the SiteOrigin Image Widget on the right that is stretched. It appears that Custom Size has been selected and 9999 is the height value in use. If that’s the case, please, check the same widget on your production site. Is the setup the same with 400 and 9999 chosen as the Custom Size values?

I don’t know why I can’t reach the site. It shows that the server is not accessible for me so I can’t see the staging site, nor can I make any changes. I can tell you that since I can remember (at least two years) I have always set one of the custom values to 9999 which automatically sets that value to the largest size it needs to be while still being proportional to the other value that is set.

The most recent update allows resizing using only one value of the Custom Size field. If for example, you choose 400 width, the height will be proportionally sized if left blank. How many widgets would you estimate have a height set to 9999px?

The staging site loads for me without issue using Safari and Chrome. I tried with and without a VPN. I also tried a VPN location in the States. Does the access issue persist in an Incognito or private browsing window?

Oh no!! Almost all of my custom sizes have the 9999 set. That’s how it’s always been set, and I have custom sizes set on most all of my photo images (which is in the several hundreds).

Understood, thanks. We’ll find a way to accommodate.

BTW – I can’t access the staging site in an Icognito window.

Thanks Andrew. I greatly appreciate your support on this.

Hi usainds,

I’ve run a few tests and I’ve come up with a snippet that’ll allow you to avoid this issue with the latest version. Please install Code Snippets and then navigate to Snippets > Add New and add the following PHP:

add_filter( 'siteorigin_widgets_instance_sow-image', function( $instance, $widget ) {
	if ( ! empty( $instance['size_width'] ) && $instance['size_width'] === 9999 ) {
		unset( $instance['size_width'] );
	}

	if ( ! empty( $instance['size_height'] ) && $instance['size_height'] === 9999 ) {
		unset( $instance['size_height'] );
	}

	if ( ! empty( $instance['size_external_width'] ) && $instance['size_external_width'] === 9999 ) {
		unset( $instance['size_external_width'] );
	}

	if ( ! empty( $instance['size_external_height'] ) && $instance['size_external_height'] === 9999 ) {
		unset( $instance['size_external_height'] );
	}

	return $instance;
}, 10, 2 );

When prompted, activate the snippet. How does that look?

I have always set one of the custom values to 9999 which automatically sets that value to the largest size it needs to be while still being proportional to the other value that is set.

This happens automatically with all of our widgets so I recommend against doing this.

Kind regards,
Alex