I'm being really cautious how I manage a switchover from an existing WordPress site to a new one.
In a nutshell....
I have designed a new wordpress website, let's call it NewWebsite.com
I have an existing website, let's call that MyBrand.com
I want to be able to point my domain name, MyBrand.com, at the NewWebsite.com server. So that MyBrand.com takes you to the newly designed WordPress instance.
I'm hosting both on TSOHost, they are both standard WordPress.org installs and I have access to root.
Any help would be hugely appreciated. I've done this once before and it ended badly, so treading carefully.
Thanks a lot for reading.
Related
Building a new website without affecting the current website (wordpress) until finished? Concerned about google web crawling, seo, ssl certificates, wordpress config, etc.
I was advised to create a new subdomain and build the new website there but I have concerns about this approach. After your build your new site (wordpress) on the newly created subdomain how do you redirect the main domain to that subdomain and not break google's web crawling or SSL certificates or anything else?
Building and testing separately from the current site is always the best approach. A separate development environment is always preferable, if possible. This also allows you to test upgrades and changes in future before making them on the live site and risking an error.
Whether you have a separate environment or not, there are 2 ways you can build the site separately from the current site:
1. Build in a separate location and then migrate the installation to the current hosting when its ready.
This is a common approach but it is quite tricky if you try to do it manually - a common question here is how to fix a broken site after a manual migration.
My recommendation is to use a plugin that is designed to do it all for you. You can have the site moved and running perfectly in minutes without all the hassle. I use the free Duplicator plugin, but there are others.
See how to migrate a Wordpress site in 4 quick & easy steps
2. Build in a subfolder of the current website and switch it to run from the root domain
An alternative option is to build it in a sub folder (a subdomain will not work for this approach). When you're ready, it just takes a few steps to make it run from the root domain without moving anything.
Note that this is then your live site, so you don't have this as a copy for testing upgrades in future.
See how to set up WP that's installed in a subfolder so that it runs from the root domain
Finally - whichever approach you take, if your new urls are different from the current site, you should set up 301 redirects so that both your users and Google can find the corresponding pages and it doesn't hurt your Google ranking.
I am trying to set up a development site on the sub-domain development.warriorsliveon.org of warriorsliveon.org.
This is a WordPress site and I copied the plug-ins, themes, and upload folders to the new WordPress installation on the sub-domain. I also copied the database from warriorsliveon.org, did a find and replace of warriorsliveon.org to development.warriorsliveon.org.
When I go to the site , http://development.warriorsliveon.org. it either switches automatically to the follow address, or other times, lets me log into WordPress, but then goes to this address.
http://development.development.www.development.development.warriorsliveon.org/
Anyone have any ideas where I should look to resolve this issue?
I'm happy to post any code, just not sure at this point what would be useful. Any help is appreciated!
Changing the Domain Name that your Wordpress installation runs under is more complicated than just editing one or two files. The best approach is to use a tool like https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
If you download this free tool and upload to your server then it does a batch find-and-replace across every single table in your Wordpress database.
So, for example, replace http://www.warriorsliveon.org with http://development.warriorsliveon.org
You can do a dry run and it will show you all the replaces that it will make. Once you're happy then click the "live run" button and all the changes are made.
I use this tool all the time when I am moving a site from my local machine to the live server. I also use the exact same approach when migrating a site from http to https
So I built this client a WordPress site and after if was completed and paid for he decided he didn't like his domain name. So he logged into HostGator and then bought/transferred to a new domain.
Then a day later he calls and wonders why his page isn't loading. I'm able to go into the FTP and save all the wp-content and every file that was originally there... My question is how do I get the WordPress site I built onto the new domain name?
I've read all kinds of tutorials about how to export/import but they require the site you're transferring from to be live.. I can't log into the wp-admin portion because it looks like the domain does not exist anymore.
I'm definitely not a back-end guy.. I've build a few sites off line with xamp but i have no idea what I'm doing when it comes to trying to salvage this site. Any help?
WordPress is flexible to handle situations like moving to another server. First back up your WordPress directory, images, plugins, and other files on your site as well as the database. The detailed steps on how to do it is well documented in the website https://codex.wordpress.org/Moving_WordPress.
I have an existing site that is hosted on a LAMP VPS. I also have a blog that is hosted on Wordpress.com/blahblahblah. The goal is to have all of the traffic that goes to the blog at least go through the site to help with counting stats, SEO, and whatnot. My complete lack of familiarity with Wordpress leads me to believe that the easiest way to accomplish this would be to create a Wordpress instance on the VPS and host the blog there. I guess I'm asking two questions. First, what are the pitfalls of hosting a WP blog on a LAMP VPS? And second, is there an easier way to have that traffic pass through the existing site without pointless redirects?
Wordpress will work fine on a LAMP VPS.
Traffic should not pass through another domain, because as you said that is a pointless redirect. I am not sure why you would not want to use one of the many analytics available such as Google analytics.
If you needed to you can setup the other domain and add an index.php file with a header('Location: wordpressite.com'); and whatever other code you want.
Another, cleaner, option is to edit the Wordpress site itself to send the information required to the other site by using a plugin or perhaps some javascript code. This is typically what third party analytics plugins do.
Goal: We have a Magento installation which contains a lot of sensitive data. We're looking to host a Wordpress installation.
Problem: Since we're installing third-party modules on Wordpress, we don't want any security issues in Wordpress to be able to compromise Magento.
I've spoken to a couple of my friends, and also had a think back to how it's been implemented in the past, but I wanted another opinion.
Since the wordpress directory will reside inside of the magento directory, would it be sufficient to chown the files inside of wordpress to a new user ("user-wp"), and then to chroot the user-wp user to the wordpress directory? Magento would then still have access to all of the Wordpress files, but not vice-versa.
Any other suggestions on how to go about implementing this would be more than appreciated! Somebody also suggested configuring a separate vhost.
Using a subdomain like blog.site.com would probably be the easiest way to set this up. All you would have to do is add a new VHost for the WordPress installation.
I don't think Chrooting would provide much security. You may also run into WordPress Plugin issues with such a configuration.
The setup is tricky. You would have to go and modify the PHP-fpm process pool and users it runs with. Then assign one pool to Magento and another to WordPress. Additionally you will also want to serve static assets & uploads from the Webserver itself.
And when you change this config you have to retest your Magento install to make sure things you didn't break anything accidentally.
Too much hassle, just use the subdomain. :)