Build a new WordPress site while the old site is live
The goal here is to make sure that the existing website works until where you want to go the new site on – with almost zero vacation. No one wants to place their site in maintenance mode while the new WordPress site is getting assembled!
As always our substance is NOT created for the designer. Although, we may dig into some more technical walks a couple of the decisions just to demonstrate how technical things CAN get in case you don't take the more enhanced courses presented. We have your back non-fashioners!
New Site Build Approach for WooCommerce versus WordPress
Significantly, there is a fundamental contrast between the recommended approaches to building a new website in the background to be later moved onto an existing domain if the website is also an eCommerce store.
In case you're enthused about the distinction between WordPress and WooCommerce you should take a gander at my detailed article here.
If it's a WordPress website without WooCommerce, you have a range of alternatives without an abundance of compromise around there. You can ultimately achieve your ideal goal of moving the new website onto the existing domain while keeping the existing website operational up until the point that you want to turn on the new site.
If you have WooCommerce installed and the site is a functioning WooCommerce website that's taking solicitations, you have to think even more carefully about what you're doing. Architects have greater adaptability in their approach as they're more comfortable playing with database tables and joining or adjusting data. For the non-engineer, you want a "front end heavy" arrangement that DOESN'T anticipate that you should bounce into lines of code. This is conceivable, anyway the work you do ought to be challenging in other ways to keep your existing WooCommerce site live while you plan a new WooCommerce website and then eventually make the new website plan live.
As a matter of first importance, we'll cover off building a new WordPress site while the old site is live (WordPress without WooCommerce)
Building a new WordPress site while the old site is live
I've used all of these options and I've listed them in my solicitation for inclination based on their ease and viability.
Equally – while picking what course to build your new WordPress website while the existing site remains life you should consider the advantage of having the choice to collaborate with others on your new site plan with it being located at a particular URL accessible from anywhere.
I collaborate with clients and team individuals alike on new activities and the advantages of installing WordPress on a subdirectory, subdomain, temporary domain, or staging site are that collaboration is easy (in contrast with the fourth decision I list beneath – using a local install).
So here we go – your 4 alternatives for building your new WordPress website while keeping your current site live!
NOTE: This also answers how to create a WordPress website without a domain (as long as the existing site is located on a domain clearly!)
Alternative 1 – Install new WordPress site on a Subdirectory of your existing domain
A subdirectory is just a record location on your existing website. What does that mean?
So for example;
websitename.com/newwebsitesubdirectory/
No doubt the URL of basically one more page – yet it's certainly not.
You can install a unique new installation of WordPress on this subdirectory and essentially build a brand new WordPress site on the existing domain.
To install WordPress on a sub-list you should advise your facilitating provider's technical documentation. In case you're using CPanel and Softaculous installer is available, you can indicate a new catalog to install WordPress on in that general area in the installer – see screen capture
One of the relatively large advantages of doing it this way is that you can move this new website onto the main domain easily by a few records in your facilitating provider's archive manager and make a minor alter to one of them.
Make an effort not to panic. This is probably the MOST technical arrangement I would propose – and I'm acquainting it with a show that this is a decision, anyway others don't anticipate that you should go anywhere near your CPanel or File Manager.
The records to duplicate are;
index.php
.htaccess
You'll duplicate these records from the subdirectory folder that your "new" WordPress website is by and by located in – recall; websitename.com/newwebsitesubdirectory/
You'll then take these records and paste them into the domain file folder.
By and by in case you're familiar with File Manager, you'll realize that the main registry for your existing website will be located in the public_html folder and probably named something the same as your website name.
So in our example, it would be in the accompanying folder;
public_html > websitename
We should also at this point rename the EXISTING index.php and .htaccess archives in the main catalog – just add a "1" to the furthest reaches of the record name until further notification.
By and by the records are located viably, we'll need to alter the index.php archive to make the new website work.
Altering the index.php record
At whatever point you have these records replicated and located in the right folder, you'll need to alter your index.php archive.
You'll have to discover this line in the index.php record;
require('./wp-blog-header.PHP)
and replace this line with the accompanying piece of code;
require('./subdirectory/wp-blog-header.PHP)
regardless, don't use the words 'subdirectory' you'll need to swap this out with the name of the subdirectory you created. for example in my example about the subdirectory I created was websitename.com/newwebsitesubdirectory/therefore I would adjust the line in the index.php record to say;
require('./newwebsitesubdirectory/wp-blog-header.PHP)
Save the record and exit!
There are a final few stages to making your new WordPress site live
At the point when endorsed into WordPress (finally, away from the record manager!) You'll need to alter your URL settings.
In the WordPress admin dashboard go to 'Settings > General' and change the URL for the 'WordPress Address' and the 'Site Address'.
You need to change the subdirectory URL to the main website domain URL.
For example, in the General Settings tab you'll see your subdirectory URL, similar to this:
https://websitename.com/newwebsitesubdirectory/
It ought to be changed to this:
https://websitename.com/
And that's it for using this approach to building a new WordPress website while the existing site is live.
The above rules were rearranged and adapted from the blog at WPMU Dev – you can see it here.
If making these minor alter to records in your file feels way unnecessarily technical – that's not an issue. You can regardless basically "migrate" the new site onto the existing domain.
I'll give more details on migrating in explaining your next alternative with regards to building a new WordPress site while the old site is live.
Alternative 2 – Install a new WordPress site on a subdomain of your existing domain
This is my favored arrangement while advising non-engineer WordPress site builders.
A subdomain would take after this: newsite.maindomainname.com
This in combination with using a "migration module" is a great way of keeping things straightforward.
In the first place, you'll need to create a sub-domain and install WordPress on that Sub-domain.
In case you're using our recommended WooCommerce Hosting, SiteGround, here are their headings on the most ideal way to create a subdomain on your existing domain using SiteGround.
Clearly, in case you're using another facilitating provider, essentially search Google for: "how to create a subdomain with <insert facilitating provider here>"
In any case, is there any valid justification why you wouldn't be with SiteGround? They're awesome and you can read our SiteGround review here.
Clearly, at whatever point you've created your subdomain, it's essentially the standard cycle for installing WordPress.
In case you're using CPanel – use the gave WordPress installer like Softaculous
In case you're using SiteGround's site gadgets – basically follow their basic one small step at a time measure at whatever point you're endorsed into your facilitating account for adding a new WordPress website to your facilitating account.
You can now build your new WordPress site autonomously of the existing website, totally in the background – keeping the existing site live while you build your new WordPress website.
At the moment that you've finished your new website plan, you can then use a "migration module" to move your WordPress site from subdomain to main domain.
Comments
Post a Comment