I recently updated Page Builder by SiteOrigin plugin to version 2.10.13 and SiteOrigin Widgets Bundle plugin to version 1.15.9. After updated, the page layout is missing this code from the plugin CSS below which causes to break the previous layout.
.panel-grid.panel-has-style>.panel-row-style, .panel-grid.panel-no-style{
display: flex;
-ms-flex-wrap: wrap;
flex-wrap: nowrap;
-ms-justify-content: space-between;
justify-content: space-between;
}
Is there a way to add the following code or to solve this issue?
Thanks,
I checked through View Page Source and found that neither of “front-flex.css” or “front-flex.min.css” is being loaded. But I see the files in the plugin folder.
I’m not sure if this could help, but I also updated WordPress version from 5.2.4 to 5.3.
Hi Kaylie
Thanks for posting your question. Please, try following the below process to see if a working baseline can be established.
This sounds like it could be a plugin conflict issue. 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 you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
I tried deactivating all non-SiteOrigin plugins and and activating them one by one. But nothing seems to be solving the issue. Also, the theme doesn’t seem like it’s causing the issue. For now, every plugin is rolled back to the previous version at which they were working fine. But the website is not still loading front-flex.css and other css files. By any chance, do I have to update the SiteOrigin database after WordPress is upgraded to 5.3?
I actually found and solve the issue. In “”Layout”” tab of the SiteOrigin plugin, I switched “Use Legacy Layout Engine” from “Always” to “Detect older browsers” and it added the front-flex.css and other missing files again. I appreciate your speedy support!
Hi, thanks for your feedback, I appreciate the updates :)
The objective of the plugin conflict test is to find a working baseline. When all non-SiteOrigin plugins were deactivated, did you check the issue? Only if the issue is resolved would you reactivate other plugins one by one, checking the problem after each activation. Put another way, the purpose of the test isn’t to reactivate other plugins one by one, the purpose is to see, does the issue resolve when we remove everything else, that’s the main goal, can you find a working baseline? If a working baseline can’t be found, you can reactivate all other plugins at once as you wouldn’t have found a baseline to test from.
By any chance, do I have to update the SiteOrigin database after WordPress is upgraded to 5.3?
No update is required.
In “”Layout”” tab of the SiteOrigin plugin, I switched “Use Legacy Layout Engine” from “Always” to “Detect older browsers” and it added the front-flex.css and other missing files again.
Awesome, I’m really glad to hear that helped. I included the above feedback in case you’d ever like to revisit or if you have to run a plugin conflict test in the future.