WordPress is mobile in two senses

The choice of the right content management system is by no means trivial. Depending on the requirements of the web, the general conditions due to the hosting package and last but not least the skills of the editors, you have to invest quite a bit of brainpower in the selection process.

A plugin that can output content optimized for mobile devices, not all systems have, but on this aspect of mobility I do not even want to emphasize here. I am more concerned with the ability to change the server, the hosting. Most people probably think primarily about switching providers, but that's just a reason to bounce back and forth. Equally valid is probably the scenario that the environment needs to be updated. Who does not know the issue that you actually want to move to a higher PHP, but the move of the website puts unexpected obstacles in your way?!

Therefore I would like to outline how easy it is to move any WordPress web to our webhosting

As a first step you should set the entries in the DNS to a low TTL value. This prevents delays due to cache times. 300 seconds would certainly be a good starting point. Normally such entries are usually cached for one day. After all, you don't want to wait that long if you end up converting the web for good.

With our web hosting packages you have the possibility to maintain your Worpress integrated through the Plesk management interface. I would recommend this to anyone who is not dependent on customized plugins. So the next step is to create the domain in our webhosting on the Plesk, if it is not the root domain of the subscription anyway. There you can then create a WordPress instance with a few clicks. How to do that is already described in our tutorials, so I'll spare that here.

Now it gets a little tricky

The problem here is the IP resolution of the installation in use. Depending on how you want your redirects (with or without www … http to https etc.), you have to do some trickery. I use the clone and sync function of Plesk to do this. First of all you have to create an additional DNS entry called staging.DOMAIN.TLD and enters as IP address the one of our hosting server. Now we clone the newly created Worpress installation on our Pleskserver. This is done by creating a new domain, which gets the name "staging" and duplicates the complete content. This may seem pointless at first glance because the new installation is still empty, but the point is to sync that back later on!

So much for the preparations on our Plesk server and in the DNS. Now we turn our attention to the active site. We need a function to push the running site to another WordPress instance via sync. For this we can use WPSiteSync. On the download site https://wordpress.org/plugins/wpsitesynccontent/ there is also a wonderful video tutorial. So we push the active site completely to our staging.DOMAIN.TLD on the new Pleskhosting.

And then we are almost through

We click back into our Plesk interface and select in the staging.DOMAIN.TLD the function "Synchronize. With this we write the complete content into our source instance from which we created the clone in the beginning. Now let the IP address in the DNS point to the new WordPress, that means set the entries for www and blank to the same value as staging, and the whole thing is done. Last but not least you should turn up the TTL to one day, so 86.400 seconds.

Life can be this simple. 😉

Leave a Reply

Your email address will not be published. Required fields are marked *