• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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