alexgso

Hi Hunter,

Thanks for trying. I’m having trouble replicating this issue after that the changes made in that release. Can you please send me a copy of your layout? You can do this by opening any page that’s affected by this issue in the editor. Click the 3 vertical dots at the top right of the screen. Select Code Editor and you’ll see the markup for the current page. Copy the markup and paste it on this page. Please reply with a link to the Pastebin.

Kind regards,
Alex

Hi Hunter,

We’ve been able to identify a situation where this can happen, and we’ll be releasing an update shortly that resolves this issue. To avoid this issue in the meantime, I recommend following the advice suggested by Andrew as that’ll allow you to revert to a version that doesn’t have this potential error.

Kind regards,
Alex

Hi Abigail,

Thanks for reaching out. I’m sorry to hear you’re having issues with SiteOrigin CSS and the MainWP Child Plugin. Can you please elaborate on how this conflict presents? I’ve run a few tests and I’m having trouble coming across the described issue, but that could be due to my unfamiliarity with MainWP.

Kind regards.
Alex

Hi,

Thank you for the report. We’ve run a few tests and identified what’s going on. This issue will be shortly in an upcoming SiteOrigin Widgets Bundle update.

Kind regards,
Alex

Kia Ora Tim,

Thanks for clarifying. I recommend avoiding any performance plugins during the initial development phase as I’ve found they can be hard to work with in general.

That sounds great. Let me know how you go. ??

Kind regards,
Alex

Hello Armands,

Thank you for the report. I’ve come up with a fix for this issue, and this fix will be included in a future Widgets Bundle update. In the meantime, I’ve prepared a build for you to use, and you can download it by clicking here.

Before proceeding, do a backup.

Navigate to Plugins > Installed Plugins, and deactivate SiteOrigin Widgets Bundle, and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload so-widgets-bundle-1.58.1-beta.zip. When prompted, activate it.

Kind regards,
Alex

Kia Ora Tim,

Thanks for reaching out. I’ve looked at your site and see you’re using LiteSpeed Cache. Every time you make a save, we change the version string for the CSS file URL to bypass the cache. If the page HTML isn’t updating due to caching. Does this issue occur if you clear your page cache?

Consider temporarily disabling the external CSS by adding some PHP to your website. If you don’t have a method of adding PHP, please install Code Snippets. Once installed, navigate to Snippets > Add New and add the following PHP:

add_filter( 'siteorigin_css_enqueue_css', '__return_false' )

Click Save Changes & Activate.

If you do have a method of PHP to your site, please add the above PHP using that method.

Kind regards,
Alex

• This reply was modified 10 months, 1 week ago by alexgso. Reason: Accidentally posted too soon

Hello Anthon,

Thanks for reaching out. It’s not directly possible to stretch widgets to be the entire height of the row (this is due to compatibility reasons). It is however possible to achieve this by stretching the Columns and applying a background to that instead of the widget.

Please open the row you would like to do this for by clicking the wrench button above the row. Go over to the Styles sidebar and open the Layout settings. Set the Column Vertical Alignment to Stretch. Click the column you would like to give a background by clicking the blue background representing the column. Avoid clicking the percentage amount or you’ll enter column resize mode.

Once selected go over to the Styles sidebar, go down to Column # Styles (# being the column number), and open the Design settings group. Set a Background Color and then repeat this process for the other Columns you would like to adjust.

Kind regards,
Alex

Hi Shaun,

Thanks for reaching out. We’re currently working on a change that will allow for parts of your suggestion to be possible. I’ve logged the rest of your feedback as possible ways for us to expand this change further. Thank you for the suggestion. ??

Kind regards,
Alex

Hi Jessica,

Thanks for reaching out. Yes, all of our plugins and themes are compatible with PHP 8.2. We actively develop while using 8.2 to ensure potential compatibility issues are caught early, but sometimes they slip through. If you feel like you’ve come across one, please provide us with a copy of the error message you’re getting and we’ll investigate this issue asap.

Kind regards,
Alex

Hi Phil,

You can apply the provided CSS to the content area by checking if the container is in #content.

It’s possible to apply the provided CSS to non-page builder powered pages by using the body:not(.siteorigin-panels) selector.

Here’s the CSS provided in my last reply with these adjustments:

body:not(.siteorigin-panels) #content .container,
.archive #content .container {
    max-width: 1300px;
}

Kind regards,
Alex

Hi Phil,

Thanks. As that’s an archive you can target it using CSS by using the .archive body class. Then you would do the inverse of what the Container Breaker code you’re using. Something like this:

.archive .container {
    max-width: 1300px;
}

This CSS is untested and may not work as expected. Some adjustments are likely required.

Kind regards,
Alex

Hi Alyse,

I’ve investigated this issue and spotted a compatibility issue with a shared JavaScript library we both use. We’re using the latest version and they’re using an older version and it appears the two aren’t compatible. I’ve reached out to the authors of the theme to report this issue and it should hopefully be resolved in an upcoming theme update.

Kind regards,
Alex

Hi Phil,

Thank you for the link.

But every page, that is not build with page builder, has no container then.

That’s happening due to a full width row being added to the footer. PB outputs the container breaker to allow for it to display as expected but that has a knock on affect of also removing the container for the regular content due that very same code. To account for this, you need to selectively re-add it back. I’ve had a look around your site and I actually can’t seem to find a non-PB powered page. Can you please link me to one?

Kind regards,
Alex

Hi Phil,

Do you have a public URL to your website that we can take a look at? This will allow us to take a closer look at your setup and confirm your settings.

Kind regards,
Alex