Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Hey – fantastic plugin!
Recently noticed something.. if I have set my full width container setting to .site in the settings, I’ve found that if I’m using a “standard” row and a site origin editor widget inside, the contents are not properly responsive. Eg. when I shrink the browser size the contents get stuck at a certain width and bleed off the page to the right. This only seems to happen in Firefox, as chrome and mobiles etc work as I expected.
If I change the row width to “full width” everything works well in all browsers.
I’m about to update all my rows to full width now (there are a lot of them!) Any ideas on what might be causing this?
Many thanks
Hi Speedy,
It should be noted that standard means theme standard. I may be able to help resolve this but please be aware of that. Do you have a public URL where we can take a look? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.
This is a private message.
Hi Mark,
That’s odd. I’m not actually able to replicate this responsive issue you’re having with FireFox. Hm. Maybe adding the following CSS will resolve it for you regardless of the fact that I can’t replicate it. If you navigate to AppearanceCustom CSS, you’ll get our custom CSS editor. Just add the following code.
.entry-content { max-width: 100%; }You might also need to install the SiteOrigin CSS Editor.
Thanks for the help Alex. Didn’t work I’m afraid, but interesting to hear you can’t recreate with firefox, so I’m investigating whether if might be some kind of browser addon issue..
Great tip about the Custom CSS option
Hi Speedy,
Hm. Could you maybe viewing it on a different computer with a recently installed copy of FireFox?
Genius Alex! – we’d switched ffox updates to off. Just updated and everything now works as expected.
So sorry to trouble you, and many many thanks for taking the time to figure out our own problems.
Would happily pay for your plugin if you had a premium option by the way J