There was a similar thread here: https://siteorigin.com/thread/multiple-columns-not-showing-anymore/
I am having the same issue – all content being rendered as single column – but I don’t use the Better WordPress Minify plugin, so the answer provided in the previous thread does not apply to me. I regularly update my plugins, as suggested by WordFence, but I don’t always view the website after the update. Some time back, my website stopped rendering properly, and despite making backups before every update, they are eventually purged, and I have no “good” backup available.
I hesitate to call this a “bug report”, but even when virtually all my other plugins are disabled, I am still seeing incorrect rendering.
If there are any known incompatibilities, I’d love to know so I can perhaps arrange to use alternative solutions.
I use the Eduma Theme from Thimpress.
The following plugins are active:
Black Studio Tiny MCE Widget
BSK PDF Manager
Captcha by BestWebSoft
Contact Form 7
Crelly Slider
Duplicate Page
Easy WP SMTP
Event Registration
LearnPress
LearnPress Pre-requisite Courses
MailChimp for WordPress
MailChimp for WordPress – Premium
Ninja Forms
Official Statcounter Plugin
Page Builder by SiteOrigin
Really Simple CAPTCHA
Redirection
SiteOrigin Widgets Bundle
Slider Revolution
Social Login, Social Sharing by miniOrange
Thim Framework
Thim Testimonials
Widget Logic
WordFence Security
WordPress Importer
WP Super Cache
Yoast SEO
The website URL is: www.wial-canada.org
Thank you for any help you can provide.
Jack
Some more information may be helpful.
After doing some research, the author of the Thimpress Eduma theme indicates that there were some CSS changes introduced into (relatively recent) versions of SiteOrigin Page Builder.
The last content added to my website was April 4th, and it rendered properly at the time. I have been updating Page Builder by SiteOrigin religiously, but not checking my website to see if anything had been broken by the updates.
How can I access and install older versions of the plugin, to see if any of the recent versions caused this problem?
Hi Jack,
As of 2.5, columns/rows now require a specific asset to be output to work – flex-layout.css. This file is missing in your markup for whatever reason and I can’t seem to see why based on your plugin list – I’m not aware of any issues with any of them.
Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If the above doesn’t help, can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Thank you, Alex, for posting a reply. Before posting my own issue, I read several similar issues from other posters and saw the suggested fixes. I have also gone through the procedure of disabling all other plugins. Rendering was still broken when all were deactivated. I have *not* taken the step of changing my theme to one of the defaults to see if your plugin will work. The last time I did that, I had a dickens of a time getting my actual child theme to work properly. I’m going to assume your plugin will work with the default theme – because of other people who said that worked.
I’m also in contact with my theme’s author on their support board to see if it’s a known interaction. Quick frankly, the easiest “next step” from a diagnostic point of view would be to get my hands on the various versions of Page Builder released since April 4th, and see which one of them is the one associated with the beginning of the rendering issue.
Thank you!
Hi Jack,
I would recommend doing a backup and then temporarily change to a default theme. Worse comes to worse and changing back to the theme doesn’t help, you can just restore the backup.
> Quick frankly, the easiest “next step” from a diagnostic point of view would be to get my hands on the various versions of Page Builder released since April 4th, and see which one of them is the one associated with the beginning of the rendering issue.
It’s very likely it’s 2.5 (released April 11th) as that was a huge overhaul update. I would recommend using something like WP Rollback to do this.
Alex,
I had never heard of WP Rollback before now. After backing up my site, I rolled back to the version just prior to 2.5 and my site is back to normal. Can I leave the SiteOrigin Widget Bundle package at its most recent version, or are they updated in some sort of lock-step manner? If it’s preferable to downgrade SiteOrigin Widget Bundle to the pre-April 11th level, please let me know what version that would be.
I will now leave a great review on the SiteOrigin Page Builder plugin site.
Thank you, thank you, thank you!!!!
Jack
Hi Jack,
I can assure you there’s something on your website causing this issue and It’s not a general SiteOrigin Page Builder issue. If you completely downgrade we’ll be unable to look into why this is happening and as a result, the issue will remain and you’ll be locked to a version pre-April 11th and if you keep updating WordPress and other plugins it’s only a matter of time until they stop working – the text widget, for example, won’t work in the latest version of WordPress (this is fixed in a recent SiteOrigin Page Builder update). I would strongly recommend trying to change the theme to see if that helps.
To answer your question, yes as there have been recent changes that require both plugins to be updated so you could run into issues.
Alex,
Based on your comments here, and the frequency of updates, I’m sure the fault does not lie with your plugin. Since my client’s domain is live and I don’t have the authority to spend billable time, my options are limited. But, like you, I’m eager to get to the bottom of this. I’m going to contact the author of the premium theme and ask permission to temporarily create a new website (with a dummy URL) using his theme. I’ll install the most updated version of his theme (I haven’t been updating the theme either, because at some point early in the website creation process, one of his bundled plugins messed up the site) and then install the most up to date version of SiteOrigin Page Builder and see if things work together. If they do, then I’ll try to get authorization for billable time to update everything.