old website is not accessible anymore I think! There is no hosting for that.
New website is accessible of course.
website is www.rowingjewellery.com.au
old website domain name is www.strokesidedesigns.com.au ( this is not set as subdomain so rowingjewellery is the main. )
so why this is still redirecting me to my shopify site???
I'm no expert, but I would guess the strokesidedesigns.com.au domain still contains old nameservers, so it points to the new website.
Removing the nameservers for that domain should prevent that from happening.
Try checking for old domain records in database and replace them if needed with this tool:
DB replace
Also refresh Permalinks in wp-admin.
Please refer to this answer
clear your all browser cache and refresh your site. I hope it would be helpful for you
Related
I built a wordpress website for my client at firsturl.com. They own another URL at secondurl.com, and have decided that they would like their website at secondurl.com instead.
They don't actually have hosting with secondurl.com, they just own the URL, but both URLs are owned through the same hosting company.
Is it possible to keep my site at firsturl.com, but make it look like it is at secondurl.com? More than just redirecting, I need the secondurl.com to always be the main URL.
I would recommend try with domain masking. Here is the reference https://en.m.wikipedia.org/wiki/Domain_masking
Thanks.
Regards,
Ed.
So I created a new subdomain on Dreamhost. One-click installed Wordpress. Fresh Copied the olddomain.com to newdomain.com exported all the tables with the drop attribute to the new wordpress database via phpmyadmin. Then followed this post to update the urls.
The site doesn't load, giving me this error message:
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies.
I would make sure to check the 'www' rules in Fully Hosted (from the web panel: Manage Domains > Web Hosting > Edit), compared with your site URL settings in the WordPress dashboard. Make sure those aren't conflicting first.
If you need further assistance, just let me know the domain name and I can take a look. Please also feel free to start a LiveChat from the panel or submit a ticket; our support team is here to help 24/7!
Thanks!
Ellice S
DreamHost Staff
I finally ended up creating an empty site and then using the WP Duplicator plugin. Worked like a charm!
I would like to know how to share a session between my website non-wordpress and my wordpress blog on the same domain www.mysite.com, so that when a user is logged in to my site he's also logged in to the blog
I installed wordpress as subdirectory on my site, url for my site is www.mysite.com and I access wordpress like this www.mysite.com/wordpressBlog
On my user_login.php in my main site I activated
session_start();
to activate cookies and on my wordpress wp_unregister_GLOBALS() I added
$no_unset = array( '_SESSION', ...
But nothing happen, when I login to my main site I still have to login to the blog
as a matter of fact my site and wordpress blog are on the same domain. I installed wordpress as subdirectory on my site url for my site is www.mysite.com and I access wordpress like this www.mysite.com/wordpressBlog On my user_login.php in my main site I activated
session_start();
to activate cookies and on my wordpress wp_unregister_GLOBALS() I added $no_unset = array( '_SESSION', ...
But nothing happen, when I login to my main site I still have to login to the blog
In order to be able to share a session cookie between both sites, they will have to run under the same domain name (e.g. mysite.com). The following would be a valid configuration if the session cookie has a scope of mysite.com
www.mysite.com
blog.mysite.com
PS. I don't recommend using Cross Scripting hacks to get around this domain scoping issue. It's limited to a domain for security reasons.
[Edit]
I should also point out that it is entirely valid to have your two sub-domains (sites) hosted on different servers
[Edit]
It is difficult to provide a succinct answer to your question because you are using a non-WP site. My best suggestion for you is to post on the WordPress StackExchange where you may get someone who has done this configuration before.
I believe your issues are centred around the scope of your Cookie from WP. Editing your wp-config.php and setting the COOKIE_DOMAIN to use "" may help with your issue as referred to by this WordPress StackExchange post.
Some posts speak of removing this settign entirely. In any case you need a way to debug your HTTP sessions to see what cookies are being sent using which scope, that is why I recommended FireBug. In any case you're still going to have to re-code your non-WP site to recognise the WP cookies so understanding what's going on is important.
I did come across this other post regarding Multisite Domain Mapping that may help with your knowledge, but this is involved WP sites only so not exactly what you need.
I have a wordpress site at http://myname.myprovider.info and I just bought the domain http://www.myname.com
Ive tried to change the URL in the backend at "Setting > General" both fields WordPress Address (URL) and Site Address (URL) with http://www.myname.com. The moment i click save, Im automatically logged out of the backend. If i try to log back in, I get a white screen.
The only way to log back in is to add in the config file the following line:
define('RELOCATE',true);
If then I go back to "Settting > General" I see that WordPress Address (URL) still has the http://myname.myprovider.com and everytime I try to change it again, the loop starts again...
What can I do?
you cant just change the url in wordpress ... you would need to move all the files to your new host
you can facilitate this in wp-admin
under tools select export and follow the dirrections
then setup wordpress on your new host
and goto wp-admin and select tools import and select the earlier exported file
If you're moving from a subdomain to the main domain, you have to move files. See Moving WordPress « WordPress Codex and How to Move WordPress Blog to New Domain or Location » My Digital Life and check with your host; the URL structure "myprovider.info" may be problematic, whoever the "provider" really is.
I had a very similar problem some time back and I'm trying to remember what the source of the problem was. Until I do, here are some ideas you may or may not have tried:
(obviously backup everything first!)
Check your code (theme, scripts, functions.php, etc.) for any instances of the old URL. Sure, we all know better than hard-coding the URL but...
Do a search through your WordPress database for the old URL. Carefully (very carefully!) replace it with the new one. In my experience some plugins aren't well behaved when it comes to storing the web site URL in the database.
Try disabling all plugins to see if one of them is causing a problem.
I assume you've set the DNS by hand, rather than your domain registrar putting in place some kind of forwarding?
After much tinkering, it turns out I didnt configure the domain properly :P Thanks for all the help anyway.
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.