Please can someone help me to clarify what issues i might have when the hosting company changes the DNS settings to point away for the current old site (basic html) and to the new WordPress version of the web site?
Both sites are with the same hosting company (I cannot change hosts or hosting names now, my client and the hosting company are long term business partners). I think the server that the current live website is unable to host WordPress. So they set up another server for WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk
Current Location of new WordPress site on hosting server: http://test.blahsystems.co.uk
I think this bit is important!!
The new website is on a Windows Server and uses pretty perma links and also the .html pages plugin. There are also some redirects going to 7 pages on the old site. Everything is currently working ok.
Nest week the hosting company are going to change the DNS settings to point to the new website http://test.blahsystems.co.uk which will hopefully become the new website with the new address of http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used Permalinks at the moment because once the DNS is pointed to the new site the links will have become permanent (well I had already set up permalinks before they told me). I have not used the full address when making any links within the site.
Will the 'Find & Replace' plug-in on the database still work ok to make any required changes? I am confused as to how the DNS change actually works, will this affect what the links are called in the database or can I still change them from:
http://test.blahsystems.co.uk
to
http://www.therealwebsitename.co.uk
I presume I will need to change the Word Press address and site address in the settings panel to http://www.therealwebsitename.co.uk, once the DNS propagation has finished.
Very long winded I know but any help would be much appreciated.
Thanks
Ok - I will do the best I can to answer these 8-)
Please can someone help me to clarify what issues i might have when
the hosting company changes the DNS settings to point away for the
current old site (basic html) and to the new WordPress version of the
web site?
When you change your DNS - it's like moving into a new house.
The whole building can change - so it sounds like you're leaving a Windows environment for a Linux environment. Which is cool.
What happened on the old site - should not really impact the new site OTHER than the fact that search engines will still try to remember the old sites structure. It will take time for the search engine to realize that things have changed and that pages are new or missing.
301 Redirection can help with this.
Both sites are with the same hosting company (I cannot change hosts or
hosting names now, my client and the hosting company are long term
business partners). I think the server that the current live website
is unable to host WordPress. So they set up another server for
WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk Current
Location of new WordPress site on hosting server:
http://test.blahsystems.co.uk
I think this bit is important!! The new website is on a Windows Server
and uses pretty perma links and also the .html pages plugin. There are
also some redirects going to 7 pages on the old site. Everything is
currently working ok.
WordPress can use permalinks. If you have moved pages around - like mysite.com/about-us and it's not called mysite.com/about - you will need to create a 301 Redirect to let search engines know.
Nest week the hosting company are going to change the DNS settings to
point to the new website http://test.blahsystems.co.uk which will
hopefully become the new website with the new address of
http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used
Permalinks at the moment because once the DNS is pointed to the new
site the links will have become permanent (well I had already set up
permalinks before they told me). I have not used the full address when
making any links within the site.
I don't think using permalinks will cause a problem. They aren't "permanent". Nothing is - it's all in a transient state.
Will the 'Find & Replace' plug-in on the database still work ok to
make any required changes? I am confused as to how the DNS change
actually works, will this affect what the links are called in the
database or can I still change them from:
http://test.blahsystems.co.uk to http://www.therealwebsitename.co.uk
Sounds like this plugin is outside of the WordPress install? If so - it should still work.
If it's a plugin your hosting provider is giving you, then there should be no problems.
I presume I will need to change the Word Press address and site
address in the settings panel to http://www.therealwebsitename.co.uk,
once the DNS propagation has finished.
Yes, make sure to update your General Settings prior to the site going live so you don't have any down time.
Related
Good day 😀
I have a WP Multisite in which a site was running. The administrators decided they would revamp the site, and they did it in a provisional subdirectory so that the original site would be available while the changes took place. So this is the current structure:
mymultisite.com
mysite.com
mymultisite.com/mysitebeingremade
Now that the site changes have been finished, I would like to attach the domain name to the revamped site. So, I try to disable the site currently attached to mysite.com, change its domain to a different one, and attach the domain name to the revamped one. So from the sites configuration I make the following changes in Sites > Edit site > Site info:
mymultisite.com
mysite.com -> mymultisite.com/mysite
mymultisite.com/mysitebeingremade -> mysite.com
But it seems as if the domain name keeps pointing to the old site. What am I doing wrong? Or is it just impossible to reuse a domain name previously used in a multisite, but not in use anymore, for a new site?
I guess that I can just overwrite the original sites with the one with the changes, but I think it is too much hassle for a seemingly simple task.
Thank you 😀
Ok, I sorted it out.
It seems that, when you delete a site from the multisite, it doesn't get deleted from the database. Specifically, one entry remains in the table [prefix]_domain_mapping in which the fields 'id' and 'blog_id' are still pointing to the old site that was linked to that domain.
By changing those two fields to the id of the new site that will be using that domain name, and provided that all the changes have been made to the configuration of that site in the site configuration to use that domain for that site, it should work ok.
Thank you,
Let's say I have an old wordpress site hosted at abc.com, where all the posts are written using visual editor. Now, we have decided to re-purpose old content and write everything in markdown.
Currently, abc.com has considerable amount of traffic as well as good ranking. So we can't modify the content while its live.
To make the process easier we have decided to replicate old site at test.abc.com (on the same server) and modify everything there.
Once everything is up to the mark, we change the document root of the Apache to point to the new Wordpress installation and change the Site Address (URL) in Setting via Dashboard.
So my question, How does this plan look?
Is there any potential pitfall that I need to be aware of ?
Wordpress uses absolute URLs. Therefore you should search and replace every URL in the database from test.abc.com to abc.com before pointing Apache to that directory. Other than that you shouldn't face any problems.
I recently pointed my 1&1 registered domain, masonsmn.com, away from justhost where I had a wordpress site built toward my new site constructed using squarespace.
I would like to view a few pages of the old site as they were previously (i.e. I messed up. In hindsight a few screenshots then would have been a good idea).
Does anyone know how I can access those wordpress pages at this point?
Thanks,
You can add a hosts entry to your computer to force it to go to the old IP address. See google for instructions for your operating system. Don't forget to remove it later! :-)
The old site is on justhost. Do you still use them for hosting? If so, just download your old wordpress files via ftp. If you already cancelled your hosting, but it wasn't long ago, they may have your files backed up still. If this is the case I would give them a call and see what they can do.
The problem is as follows: A new WordPress site will be installed on the same Nginx server as the current one. The current one (based on Joomla) has some complex database functionalities which will be reused. I.e. the new site will retrieve a section of it's content from the old site, with PHPs file_get_contents() or HTTPRequests.
I have no knowledge about the current site, so I'm afraid that when I try to give it a new address, I will break things. This is what this question is based on, so if I'm already wrong here, please say so.
Now my idea is to just install a wordpress site with the wordpress address configurations set to the domainname, but without setting the servers pointers for that domainname to the new site. Now I will add a rewrite rule to the current site, which rewrites all incoming traffic to the new site (directory on the server), except when the request comes from localhost, so the new site itself CAN get to the current site.
I'm relatively new to this kind of things, thinking of my proposed solution raises questions too. My question is whether my solution will work, and / or is there a better way of doing this? Unfortunately I can't just go test it.
Thanks
In theory that approach will work but it sounds rather fragile. Rewrite rules can be very tricky to get right even if you know what you're doing, so the "unless it's coming from localhost" may throw you for a loop.
You say you're not sure the existing site will break if you move it to a new domain or subdomain, but there's really no harm in trying, since you can leave the existing domain intact while you try.
So if the existing site is at example.com, try setting up a second virtual host that serves it from internal.example.com. If it works (or at least delivers the content your'e trying to scrape), go ahead & set up the Wordpress site and get the content using the "internal" URL.
The real problem though is that now you're stuck maintaining both a Joomla site and a Wordpress site. What is the complex database functionality you're trying to reuse? Is it at all possible to migrate that into a standalone PHP block that you can then call from Wordpress?
I have recently redesigned a website on wordpress. The redesign is in a subfolder of the domain. When I flipped the new website live by following this tutorial 'Using a pre-existing subdirectory install' - (http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory) everything worked as planned.
However, I am still getting the old site when I navigate to the site using www in the url.
This is a likely problem with your hosting setup. Sounds like you don't have your "A" records setup quite right. Check out this GoDaddy support article for an example. It'll be similar across all hosts.
http://support.godaddy.com/help/article/680/managing-dns-for-your-domain-names
Click on "To Add a Record" and read that. Some hosts will require you to have a "#" and a "www" record to make the site direct to the same place with or without the www.
Also remember that it can take up to any hour for records to get updated.
If all else fails, give your host a call!