Hi there,
Thanks again for this fantastic page builder. Definitely my favorite to use when I need one!
I noticed that it has issues with post/page cloners of all kinds. I’ve tried Duplicate Post, Duplicate Page, and TAO Schedule Update. I like to use plugins like these to duplicate pages quickly, and especially the schedule update which allows me to schedule an update on a page.
However, when bringing Site Origin Page Builder pages with text widgets or Custom HTML widgets into any sort of clone environment, you end up with something like this:
u003ch3 style=u0022text-align:centeru0022u003eSign Upu003c/h3u003e
Here’s an example of a custom HTML widget contents prior to using a duplicator:
<div class="non-semantic-protector"> <h3 class="ribbon"><strong class="ribbon-content">2 Month Membership</strong></h3> </div> <p class="price">$295<span class="asterisk">*</span>
And then what comes out when it’s duplicated/cloned/scheduled:
u003cdiv class=u0022non-semantic-protectoru0022u003enu003ch3 class=u0022ribbonu0022u003eu003cstrong class=u0022ribbon-contentu0022u003e2 Month Membershipu003c/strongu003eu003c/h3u003enu003c/divu003enu003cp class=u0022priceu0022u003e$295u003cspan class=u0022asterisku0022u003e*u003c/spanu003eu003c/pu003e
I know u003c etc are unicode characters, but I’m wondering why it’s translating these in custom HTML blocks especially. Any ideas?
Hi Hasoptimization,
I’m sorry to hear you’re having trouble cloning SiteOrigin Page Builder powered posts and pages. Can you please send me an export of one of the pages you clone that results in this? To export a page, please open up the linked page in the editor and click the Layout button in the Page Builder toolbar. Then click import/export and then click download. Please upload the export to a 3rd party file hosting site such as WeTransfer (no email is required).
As a temporary workaround, you can clone page builder layouts to existing pages. This means that you can clone the base page, and then remove the (invalid) layout and clone the correct version. It’s not ideal, but it should allow you to work around this issue for the time being. You can clone a page builder layout by opening the page you want to clone your layout too and then click the Layouts button in the page builder toolbar. Select the relevant clone post type link and then find and clone the layout you wish to use for this page.
Hi Alex,
Thanks for the quick reply. This is a partial layout, but has the same issues after cloning. I’ve put it up at DropBox for you to access: https://www.dropbox.com/s/1p4ff2e9bavtx3x/5744.json?dl=0
I appreciate the workaround too. Thanks for that.
Hi AC,
Thanks, I’ve been able to download the provided layout without issue. I’ve run a few tests using it and I was able to clone it without issue using Duplicate Post. Are you able to replicate this issue using the provided layout?
If so, can you try disabling all non-SiteOrigin plugins (except for the clone plugin you’re using) 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.
Hi Alex,
I’m a bit confused. I exported the JSON after duplicating the page layout using a cloner, which produces this problematic export very clearly in the JSON, take a look at line 1:
{"widgets":[{"title":"Step 1","text":"u003ch3 style=u0022text-align:centeru0022u003eSign Upu003c/h3u003e"...Did you want the JSON of the page layout prior to using the duplication/clone/whatever? Here’s the JSON of that prior to any duplication effort: https://www.dropbox.com/s/iazwcjikdql4gcv/5701.json?dl=0 which line 1 looks fine, but again I’m not using import/export on these pages, instead trying to clone the whole page and/or schedule updates with it, which causes the same unicode output issues.
I find this is very consistent from site to site… One of those things that always irked me with this page builder.
Hi AC,
Ah, that explains that then. The Page Builder Import/Export process filters data on import which is likely why I didn’t see that after I had initially imported. I tried using the layout included in your last reply, and it imported and cloned without issue. At this stage, I strongly suspect you’re experiencing a plugin conflict as I’ve been unable to replicate this issue using the layouts you’ve provided. Please run a plugin conflict test.
Hi Alex,
I’ve turned off every plugin on this site with exception to Site Origin Page Builder and Duplicate Page just now. I duplicated the page, and the text and custom HTML widgets are still exporting all HTML characters as unicode.
Any other ideas?
Hi Alex,
Doing some more testing trying to get this to show up and give you a good idea of where it shows up. I tried with a fresh setup to see if I can pinpoint where this error happens.
I think this might have something to do with using a Site Origin Page Builder Gutenberg block rather than having the whole page be a site origin page builder page. I can get a full site origin page builder page to duplicate without any issue, but if I use the block instead, I’m getting this error.
Does what/where I’m seeing this issue make more sense? I probably should’ve volunteered this information to begin with, but I honestly forgot there were full page builder pages since I’ve been using Gutenberg blocks to intermingle.
Hi AC,
Unfortunately, I was unable to replicate this issue using the SIteOrigin Layout block either. Have you been able to replicate this issue for websites hosted with a different hosting provider?
Hi Alex,
Yes, I have at least three sites I can confidently report this as an issue on – two are using Hestia theme and one is using Talon theme. These are hosted by a reputable web host, definitely not a GoDaddy setup or anything like that.
The website I just set up for testing is a local instance using Flywheel Local which I’m still able to reproduce this issue with using only Twenty Twenty theme, Site Origin Page Builder, and Duplicate Page.
Is it helpful to you if I can provide a video of what I’m seeing? I’m trying to think of any other ways we can sort out what’s happening with these widget areas.
Hi AC,
Thank you for the additional information. I tested locally using Local by Flywheel, and on a DigitalOcean Droplet. Can you please send me an export of the test site using Local by Flywheel?
Yes, please also send me a video of what you’re seeing. I’m still able to see the text when editing widgets, and the invalid code isn’t in the export for me either.
Hi Alex,
I’ve got both ready for you. Here’s the video which shows how I can reproduce the issue: https://www.dropbox.com/s/haqt6dzkk7tdy9k/siteoriginpagebuilder-duplicatepage.mov?dl=0
Directly after the video I just went straight to exporting the site, so you should have the sample page with the HTML as it should be, then the sample page in draft that was the problematic clone. Here’s the zip of that fresh site: https://www.dropbox.com/s/xjns1yhoh855x4y/Site%20Origin%20Page%20Builder%20Test%20Site.zip?dl=0
UN admin, pass password, just for ease.
Hi AC,
Thanks. I’ve been able to verify this issue with the provided export. It appears to be a general compatability issue with Duplicate Page plugin. I installed the Duplicate Post plugin and was able to clone the Sample Page without issue.
Hi Alex,
Thanks for checking. I noticed this happens with other duplicators (for example, TAO Schedule Update) so it appears they may use similar methods for cloning.
Would it make more sense to submit requests to those plugin authors instead?
Hi AC,
Yes, please report this issue to those developers. With that said, I’m going to log this with the development team also.