Relocating Site to New Host...
Permalink
I think I did everything correctly:
1. I exported the database and imported the contents into the new database. Worked like a charm.
2. I opened the config file and changed the lines accordingly with the help of customer support from my hosting company so I was sure to put the correct info in there.
RESULT:
When I visit the URL, I am welcomed by the Install Concrete page.
Q: Shouldn't this Install Concrete form get bypassed since I already changed the config file?
Q2: Will it override the content of the database I already imported if I fill out the forms on this page?
I really expected to go to index.php and have it be the same front page as it was on the old hosting location.
1. I exported the database and imported the contents into the new database. Worked like a charm.
2. I opened the config file and changed the lines accordingly with the help of customer support from my hosting company so I was sure to put the correct info in there.
RESULT:
When I visit the URL, I am welcomed by the Install Concrete page.
Q: Shouldn't this Install Concrete form get bypassed since I already changed the config file?
Q2: Will it override the content of the database I already imported if I fill out the forms on this page?
I really expected to go to index.php and have it be the same front page as it was on the old hosting location.
You may also want to double check your directory, file, owner and group permissions for /config /packages, /updates and /files. The /config/site.php file may exist, but lack the permissions for c5 to function properly.
PERMISSIONS for Directory, file, owner and group... since I just downloaded all the files and exported the database from my old hosting account, shouldn't they all be the same as they were? I just uploaded the files to the root and imported the database.
Using FTP upload source and then download to the new site will get all the files and correct, but not always get the permissions correct. Depends on the FTP client. I always like to double check. If you are using a tarball to move a site, things can get very interesting if your not careful :)
Cool, thanks for giving me something to look into. I'll go double-check those permissions... now, just got to find out where that info is on this site... hope I bookmarked it.
• config/site.php is definitely in the right place and has all the pertinent details corrected to the new host's db name, paths, etc. Verified by support from new host.
Q: Would it make sense to clear the database, let the C5 Wecome form create what it wants and then wipe it and import the data again? Probably not.
Q: Would it make sense to clear the database, let the C5 Wecome form create what it wants and then wipe it and import the data again? Probably not.
Have you looked at:
http://www.concrete5.org/documentation/installation/moving_a_site...
I don't get why c5 is trying to run the install script again. Can you get into the dashboard login?
http://yoursite/index.php/login...
Clear site cache maybe.
http://www.concrete5.org/documentation/installation/moving_a_site...
I don't get why c5 is trying to run the install script again. Can you get into the dashboard login?
http://yoursite/index.php/login...
Clear site cache maybe.
Thanks for the link. All seems pretty obvious except for Step 3. Disable. ... uh, disable what?
and Step 4. Disable Pretty URL's... crap. I had that enabled when I downloaded. Does this mean I have to disable, then re-download all the files from the old host and then re-upload them to the new host? If so, that really, really sucks for many reasons beyond just inconvenience. That shouldn't affect anything to have pretty url's enabled, should it? Really? Come on! No. Can't be. I refuse to believe it.
and Step 4. Disable Pretty URL's... crap. I had that enabled when I downloaded. Does this mean I have to disable, then re-download all the files from the old host and then re-upload them to the new host? If so, that really, really sucks for many reasons beyond just inconvenience. That shouldn't affect anything to have pretty url's enabled, should it? Really? Come on! No. Can't be. I refuse to believe it.
Disable Site Cache from the dashboard/debug tab. Clear site cache button is there also.
Crap. So, I really have to do all this and re-download all the files and then re-upload them to the new host?
I still have a sneaky suspicion that c5 is having trouble finding your /config/site.php
You can manually clear the cache by deleting all the files under /files/cache directory
You can manually clear the cache by deleting all the files under /files/cache directory
Good thinking, but I just deleted everything in the fles/cache directory and same problem.
index.php and index.php.dashboard are both the set-up form.
Is there a way to manually disable pretty URLs? Maybe that would work.
index.php and index.php.dashboard are both the set-up form.
Is there a way to manually disable pretty URLs? Maybe that would work.
Same result it you usehttp://www.mysite.com/index.php/login...
Does your .htaccess file have anything in it? I wonder if you need to change the old URL references in there to your new ones. You can try renameing .htaccess to something else and see what happens :)
PS: I don't give up easy... Viva c5!
Does your .htaccess file have anything in it? I wonder if you need to change the old URL references in there to your new ones. You can try renameing .htaccess to something else and see what happens :)
PS: I don't give up easy... Viva c5!
Interesting idea, but no dice. I just plopped an .htaccess into the root directory with nothing in it and no difference. I reset safari and tried it in a new browser, too (Firefox).
Try putting something like this in your .htaccess:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]
</IfModule>
Nope, nothing.
Wow, I'm starting to believe that this will actually be impossible for me to accomplish without hiring a C5 specialist.
Wow, I'm starting to believe that this will actually be impossible for me to accomplish without hiring a C5 specialist.
I shuffle sites all the time. I have had some little quirky things to adjust, but nothing like what you have going on. If you had it working in one place and it's not working in the new place, perhaps there is an apache/PHP configuration difference between the two platforms.
Are running out of the webroot or a sub-directory off webroot? I still think c5 is not finding /config/site.php
Are running out of the webroot or a sub-directory off webroot? I still think c5 is not finding /config/site.php
They're both on the webroot.
I'm hoping and guessing that it might be the fact that I am currently using an IP which is not static.
My config/site.php file looks like this (numbers and passwords changed to protect the innocent):
<?php
define('DB_SERVER', 'localhost');
define('DB_USERNAME', 'u1678908_cin66');
define('DB_PASSWORD', 'fakepassword');
define('DB_DATABASE', 'dbu1678908_concrete_5');
define('BASE_URL', '123.456.789.10'); /* change this to a domain like 'http://www.yourdomain.com' if IP # doesn't work */
define('DIR_REL', '');
define('PASSWORD_SALT', '1Xzy9Z6Lkl8oOstuF3JUPhG57qDfYgBaCQNw4KcnIim0MpxAHbeEvRTV2jWSr');
?>
So that IP# is dynamic, I guess. It's not a static IP. Do you think that's likely to be the culprit? If so, I guess I have to buy a new domain and point it to the new hosting account and then paste that domain in the above spot where the IP is... AND THEN, if that works, I guess when I eventually point the REAL domain name to the new host I will have to change the URL path again to the new domain name and HOPEFULLY that won't screw anything up.
You can see why I was trying everything else FIRST.
I'm hoping and guessing that it might be the fact that I am currently using an IP which is not static.
My config/site.php file looks like this (numbers and passwords changed to protect the innocent):
<?php
define('DB_SERVER', 'localhost');
define('DB_USERNAME', 'u1678908_cin66');
define('DB_PASSWORD', 'fakepassword');
define('DB_DATABASE', 'dbu1678908_concrete_5');
define('BASE_URL', '123.456.789.10'); /* change this to a domain like 'http://www.yourdomain.com' if IP # doesn't work */
define('DIR_REL', '');
define('PASSWORD_SALT', '1Xzy9Z6Lkl8oOstuF3JUPhG57qDfYgBaCQNw4KcnIim0MpxAHbeEvRTV2jWSr');
?>
So that IP# is dynamic, I guess. It's not a static IP. Do you think that's likely to be the culprit? If so, I guess I have to buy a new domain and point it to the new hosting account and then paste that domain in the above spot where the IP is... AND THEN, if that works, I guess when I eventually point the REAL domain name to the new host I will have to change the URL path again to the new domain name and HOPEFULLY that won't screw anything up.
You can see why I was trying everything else FIRST.
Actually, I don't think that should be the problem because I can't even view the site with that IP#. They gave me a temporary link:
http://d1007508-1.site.myhosting.com...
I just pasted that in the site.php file instead of the IP# and it made no difference. I would imagine that url is just as good as any domain I'd buy and point there.
http://d1007508-1.site.myhosting.com...
I just pasted that in the site.php file instead of the IP# and it made no difference. I would imagine that url is just as good as any domain I'd buy and point there.
ok, we may have something here. We ran a temporary site not assoicated with a domain and had to do something likehttp://xxx.xxx.xxx.xxx/~username... (where xxx.xxx.xxx.xxx is your IP address and username is your login) to hit the site. We also had to put that as our BASE_URL in /config/site.php. Also, should there be an "http://" in front of your IP address?
We need a myhosting.com expert to help configigure site without your domain name enabled. I know nothing about myhosting.com, sorry...
2. Install will not allow you to overwrite an existing database... I've tried accidentally and it told me it had to be a blank db.