Home>Support>Problem with SiteOrigin PageBuilder cloning pages since upgrade

Problem with SiteOrigin PageBuilder cloning pages since upgrade

Hi,
I’ve been using SiteOrigin PageBuilder for some time quite sucessfully and really like it. Yesterday I upgraded WP from 4.2.x to the latest 4.4 and also all my plugins at the same time. I did this first on a localhost installation with everything fine and then on a my live site. All went well with no errors and the existing pages are fine.

On the live site, when I now try and create a new page by cloning an existing page, the form doesn’t refresh and show any pages to clone – the icon just keeps spinning. The Layouts Directory option is showing fine and the Clone Blog option also returns although I have no entries to clone, it just the Clone Page option that has a problem.

On the localhost installation created before the upgrade and then upgraded, everything is fine with the clonable pages showing.

I can see no Java errors in the console page as suggested on another thread.

Any ideas?

Thanks in advance.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 8 years, 9 months ago Greg Priday
    Hi, I Work Here

    Hi Tapir47

    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.

  2. 8 years, 9 months ago tapir47

    I suspect that my hosting company may have changed something since raising this thread as disabling and then re-enabling everything solved the issue. Can’t believe that just that solved it and I didn’t check the problem was still there before disabling things which I should have.

  3. 8 years, 8 months ago SiteOrigin
    Hi, I Work Here

    Hi tapir47

    Thanks for the big wait. We’re glad to hear the issue has been resolved. All the best.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More