I have dug and dug through the search forums and I cannnot for the life of me get these rows to expand out to a wide page. I have tried full width on row settings and it does not work – full width strecthed and it does not work. I have tried css codes that the forum has mention and put my own selectors in- but does not work. Site origin page builder works fine as long as you have a narrow like page but when you want to go almost full width – they do not stretch out no matter what I try to do. Can you make these to be responsive? I can already increase my site width with no problem, but the rows will not expand out to display correctly. After years of using this page builder I will have to now do without because some type of sites need to be full width or a much wider width with a sidebar – not the standard blog look. SiteOrigin will not accomodate this. Can you fix this or tell me how to fix this?
How to expand the rows for wider pages
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Ned
Thanks for posting.
Please, let me know the theme you’re working with. On a rare occasion, the full-width container setting needs to be adjusted to accommodate the theme in use.
I am using Mission news by Compete.
Thanks. At SettingsPage BuilderLayout I have Full Width Container set to
body
and all seems normal. Please, can you send a link to a page with a full width stretched row and I’ll take a look.Thank you Andrew – I have replied to an email to give you the login info if you want to go to the backend and look around. I appreciate your time.
Hi Ned, thanks for your reply. I haven’t found that email so far. We do occasionally offer login support here on the forum but only for edge cases. We try to keep that level of support for our SiteOrigin Premium product, it helps us remain viable. For the setting I described above
body
is the default value. When testing with your theme it seemed to work normally. If we can inspect the issue, hopefully, we’ll spot the problem. Thanks again.