keithyd6699
Forum Replies Created
-
Forum: Everything else WordPress
In reply to: Installing ww.wp.xz.cn site on existing .com domainThanks to the link from threadi, I found info about my question. It seems I could migrate a site from ww.wp.xz.cn to .com, but I would have to have a more expensive hosting plan to do it, which I’m trying to avoid. Also, any plug-ins I used in building the .org site would have to be disabled, which rather goes against my wishes. So I’ll stick with .com for a while – it’s only a small, 3 page site anyway, and I doubt many people would visit it (it’s an author site, with links to my books and an About page, nothing exciting). Here’s what WordPress.com say about the process of migrating:
Prerequisites
To follow the steps in this guide, you will need:
- Your source site: a WordPress site with any hosting provider. Multisite installations are not supported.
- Your destination site: a WordPress.com website with our Business or Commerce plan. This site will be erased and replaced with the site that you import.
- All incompatible plugins must be deactivated on the source site.
If any WordPress core files (such as
wp-config.phpandfunctions.php) on the source site were modified, those changes won’t be migrated to the destination site. The migrated site on WordPress.com will run the most recent version of WordPress core and the latest compatible versions of PHP.Forum: Everything else WordPress
In reply to: Installing ww.wp.xz.cn site on existing .com domainThanks for the quick reply. I realise I’m being optimistic but I thought I’d ask the question. As I mentioned, my website was hacked twice in 5 months, and while their Live Chat tried to be helpful all I got, at least initially, was ‘We’ll run a scan of the files and you can find the list of infected files [here:] and then disinfect them. ‘ The list turned out to be several hundred files, and they gave me no idea how to disinfect the files anyway – at least until a day later, when they sent an email explaining the process AFTER I’d transferred my domain to WordPress.com. I didn’t want to take the chance again, so I started afresh. Having new DNS addresses on WordPress.com ensured that the site didn’t point to infected files again.