Brian gives a step by step guide to moving a domain into its own separate webspace
About the Author: Michele Neylon
Known for his outspoken opinions on technology and the Internet, Michele Neylon is the award winning author of several blogs and co-host of the Technology.ie podcast. A thought leader in the Internet community, Neylon is active within ICANN and an expert on policy, security, domains, ICANN, Nominet and Internet Governance. You can stalk him on various social media networks including Twitter and Instagram
3 Comments
Comments are closed.
An excellent tutorial, Brian, but with one tiny caveat –
in fact, WordPress has a nasty habit of storing absolute file references in its database, and of course the absolute reference includes the webspace number.
For example, in my database there is a record in the Options table with a name of ‘recently_edited’ and a value consisting of several of the offending values. These values would need to be changed to reflect the new webspace?
Just thought I’d mention?
Grandad
Good point.
From what I recall there are a couple of references to paths that might need to be updated in CMS that store them in the DB.
I’ll see if we can do something to cover this
Thanks for your comment
Michele
Great tutorial Brian. What are the pros/cons of having multiple sites in the same webspace? I’ve setup all of my domains in separate webspaces just to make sure they dont get messed up accidentally. Are there advantages to using a single webspace for multiple domains that I might be missing?
Also, I’d love to see some screencasts that cover an initial setup from domain reg to hosting setup and linking them together. Is the order important? Also, whats the best way to handle a domain transfer? Timing is obviously important so should the hosting be setup first before the domain is moved?
And lastly a screencast on how to handle a domain transfer ensuring that email isnt lost – a killer for my clients that I am desperately trying to get off hosting365 and onto Blacknight.
Thanks
Shay