Hi All,
I changed mt primary domain from abc.com to xyz.com.
I was told by my hosting company to drop all the files in the folder xyz.com into public_html of abc.com.
I did this and now when I navigate to xyz.com I am automatically redirected to abc.com with the following message:
Drupal already installed:
* To start over, you must empty your existing database.
* To install to a different database, edit the appropriate settings.php file in the sites folder.
* To upgrade an existing installation, proceed to the update script.
* View your existing site.
I called my hosting company and they said that the redirect from xyz to abc is a code issue. I am currently on hold with them now.
Any advice appreciated.
Comments
When I click view existing
When I click view existing site: I can't.
When I click update database script I get this message:
What is left under
What is left under xyz.com?
Drupal will not by default do that redirect, did you edit the .htaccess file under xyz.com
If you look under abc.com/sites/all/defaults do the database settings in settings.php look correct?
Are xyz.com and abc.com on the same web server? Do they use the same database server?
Thank you Nevets! The
Thank you Nevets!
The problem was the settings.php file. When I deleted the files for the old site - I was not allowed to delete the sites folder which contained the old setting.php file. I also could not upload the new sites folder for the new site.
So I manually deleted the old setting.php file and the pasted the new one from the new site in there and it worked and the site came up.
I appreciate your help.
Testings
When hoster or admin say the problem comes from my code, I first make some tests with really simple extra code.
What happen if :
- you create 2 html page with a link to each other ? are you redirected ?
- If yes, try to remove the htaccess file, if still redirected, well your hoster can't say it comes from you code as it is basic html
Hope it can help
Thank you for this test. I
Thank you for this test. I tried and the redirect issue was on their end as well. It did eventually get resolved. I appreciate your help.