• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

What is the best process for moving a Wordpress install from dev.site to httpdocs/?

Cyberchute

New Pleskian
What is the best process for moving a Wordpress install from dev.site to httpdocs/?

We start with cleaning the target directory (httpdocs) and installing a clean Wordpress, then going to the DEV.website and removing the dev. from the General Settings.

From there we seem to be fighting to get Plesk to see things where we need it to see them. Something in Onyx is different than what
 
Last edited:
We use external development server - just to mention it.
Am using the (paid) Wordpress Duplicator plugin. Works a charm!

target site:
empty httpdocs folder.
create new empty database. make note of database name, user, pw

dev site:
load duplicator, choose (create new) FTP storage. Point to httpdocs folder of target site.
run duplicator.

back to target site:
check in FTP: there are now two files. take note (copy name) of duplicator-created-file.php
in browser, go to targetsite.tld/duplicator-created-file.php
when asked, choose "new database" and enter info you took notes of when creating new database.

Done.

If there is still a glitch (extremely rare), load "better search replace" plugin and adjust/replace what's needed

Cheers,
Tom
 
What is the best process for moving a Wordpress install from dev.site to httpdocs/?

We start with cleaning the target directory (httpdocs) and installing a clean Wordpress, then going to the DEV.website and removing the dev. from the General Settings.

From there we seem to be fighting to get Plesk to see things where we need it to see them. Something in Onyx is different than what

The most easiest way to move your WordPress site from one domain to another withing the same Plesk server - using the cloning feature of WordPress Toolkit: WordPress Toolkit.

For more generic case, if you need to move a common web-site from any server into Plesk, we have the site importing tool: Importing Websites. It allow you to move WordPress, Joomla!, Drupal, PrestaShop or Magento web-sites as is: you just need to specify a source domain name and Site Import Plesk extension make the rest work for you automatically.
 
Back
Top