Hi,
I selected “Default To Page Builder Interface” under settings. So any new page I create will load the page builder automatically and when I’m done I see this text “SiteOrigin Page Builder” beside the page name under the pages menu SiteOrigin Page Builder and I can clone that page. However, for other pages that were created before changing the setting, it gives me a message to “add site origin layout block” in a blue box and when I click on that and I am able to use site origin but when done it doesn’t recognize that I used Page Builder and as result did not create a clone. Why do in one instance the page is recognized as being built with Site Origin and the other it is not? I am working on a long list for the restaurant page and unfortunately, it didn’t clone even though I did select “add site origin layout block”. I plan to use this restaurant page to create sub pages and don’t want to recreate. Is there a way to somehow copy this page so I can clone it since it is not showing as a page to clone.
Thanks, Daisy
Hi Daisy
Thanks for reaching out.
The Block Editor is the new WordPress editor (Add SiteOrigin Layout Block), the Classic Editor is the other interface you’re seeing.
You can clone Block Editor SiteOrigin Layout Block designs by clicking LayoutsImport/ExportDownload Layout. Once the JSON file is on your desktop, you can import it using the same method, by going to Layouts in Page Builder, then Import/Export.
You can convert all of your pages into Classic Editor pages by using the Classic Editor plugin. https://wordpress.org/plugins/classic-editor/. However, pages built in the Block Editor won’t automatically migrate into the Classic Editor version of Page Builder, they’ll need to be manually migrated using the LayoutsImport/ExportDownload Layout method.
Hopefully, the above helps a bit. Let me know how it goes.
Thanks, Andrew
I tested it and it works perfectly. I was worried that I needed to recreate that page.
I do have another question around the Site Origin Call To Action Widget.
When I choose the left alignment position for the button it doesn't align flush with the content. It's about 1/4 to 1/2 inch to the right of the content. The only way I can get it flush is to adjust the margins which is a lot of work. Am I missing something in the settings? I would use the
Site Origin Button widget since it aligns perfectly with the content but the styling & color of that widget is controlled by the theme and I don't want to disable the styling option. Also, why doesn't the Call To Action widget have a center alignment option?
Thanks, Daisy
Super, I’m glad to hear you’re making progress.
I’ll pass on your feedback with regards to more alignment options within the CTA widget. Would it be possible to send a link to the page you’re working on?
Hi Andrew
Here's a link to a test page where I was experimenting with the different buttons
http://vp.wowie.co/sample-button/
The green button is using the Site Origin Button widget, flat style,
left-aligned. That widget flat button style is defined by the widget and can't change the color or font unless I disabled using the theme styling for page builder, which I don't want to do. This button lays flush with the content.
The orange button is the CTA widget which is not defined by the theme so I have flexibility with font and colors. Also flat style and left-aligned.
You can see how the orange button is indented and doesn't come flush with the rest of the content. As mentioned, I can make it flush if I adjust the margins.
Is there an extra setting I am missing or is this the expected behavior?
Thanks, Daisy
Thanks for the link.
With a little custom development, it would be possible to adjust your child theme CSS to allow for some Button widgets to set their own background colors.
The CTA widget has overall padding that can be adjusted but there isn’t a “No Padding” option, only a “Low” option. You could perhaps use the Visual Editor in SiteOrigin CSS to target the CTA container and set the padding to “0”. The selector in question is
.sow-cta-base.We’re able to directly assist with adjustments like this within our premium support scope. Our free support scope is a bit more restricted due to budget limitations.