Home>Support>Moving server to server with custom plugins and root path/domain name

Moving server to server with custom plugins and root path/domain name

Hi all,

I have a dev site on a developmenbt server that is about to go live. Its a WordPress build (latest version) using Page Builder with our own custom plugins we’ve built locally for this site.

I want to move the site to a new server, with a different domain name where files will be located at a different server path. For example:

Dev server:
URL: test1.mysite.com
Path: /home/sites/devsite.com/htdocs/

Live server:
URL: www.mysite.com
Path: /srv/sites/mysite.com/htdocs

I followed the thread here:

I’d like to move my website that’s using Page Builder, what’s the best method?

And used Duplicator to take a full site dump from the dev server. Installed the archive on the new server using the installer.php and the site is available (and I can access wp-admin) however SiteOrigin PageBuild doesn’t(hasn’t) loaded in any of our custom plugins, and so the site breaks, no content is coming in correctly etc.

Is there anything I need to do to allow for custom plugins to work? Or settings to change?

Thanks,

Ben

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, 3 months ago Alex S
    Hi, I Work Here

    Hi Ben,

    That looks to be a failed migration if that’s the case. Duplicator does a 1:1 clone and then migrates the data so if there’s a difference something went wrong. We’re not able to provide migration support outside of providing basic guidelines so your best bet in resolving this issue would be to contact Duplicator via their WordPress.org forums as they should be able to provide direction.

    With that said, could you please clarify what these custom plugins do? (so I can maybe work out why they aren’t)

  2. 8 years, 3 months ago benjibarnicals

    Hi Alex,

    Thanks for getting back, I managed to figure out the issue. The custom plugins, that are being referenced by a hook had a full server path being used, updating this to the new server path fixed the issue.

    Typical, always the simple thing overlooked!

    Ben

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