Moving to new hosting server
Permalink
Hello,
I have moved my hosting to a new server (in Godaddy). Not the first time I've done this and I have followed all of the steps in:
http://www.concrete5.org/documentation/developers/5.6/installation/...
However, after doing all of the steps I only get a white page when I visit my website. I verified the database import looked the same as the old one and that all of the files where transferred over.
Anyone run into this? Or has any specific things I can check?
I have moved my hosting to a new server (in Godaddy). Not the first time I've done this and I have followed all of the steps in:
http://www.concrete5.org/documentation/developers/5.6/installation/...
However, after doing all of the steps I only get a white page when I visit my website. I verified the database import looked the same as the old one and that all of the files where transferred over.
Anyone run into this? Or has any specific things I can check?
Hey Hutman, I did not turn off Pretty URLs since I did not have access to the backend of the site. Is this something I can turn OFF through phpmyadmin or another way?
I'm not sure, I've never tried to do it without using the Dashboard. Did you find anything in your PHP Error logs?
To turn off Pretty URL's through phpMyAdmin, head to the Config table and set URL_REWRITING to '0'
While your in there you can set both ENABLE_LOG_ERRORS and SITE_DEBUG_LEVEL to '1' to allow c5 to display and log php errors.
Also check the error logs through GoDaddy's Control Panel.
Even with all this, I am not optimistic about GoDaddy. Lots of complaints about them if you search for 'GoDaddy problems' on these forums.
While your in there you can set both ENABLE_LOG_ERRORS and SITE_DEBUG_LEVEL to '1' to allow c5 to display and log php errors.
Also check the error logs through GoDaddy's Control Panel.
Even with all this, I am not optimistic about GoDaddy. Lots of complaints about them if you search for 'GoDaddy problems' on these forums.
Altering the config table is a good option but if the bug is triggered before the config file is loaded this will not matter. You want these settings enabled before the config is loaded and after.
I'm not suggesting that changing the table values will solve the problem. I'm suggesting that turning on the logging functions and the display of errors will help diagnose the error. If riro can't get to the Dashboard to turn these functions on then changing the Config table values is a good temporary debugging measure.
IMHO, this has the potential to turn into a very long, very frustrating thread that will end with moving away from GoDaddy just like many threads have concluded in the recent past. As I say, search for 'GoDaddy problems' on these forums and you will see what I mean. It's almost always cheaper and faster to just cut your losses and move to a new host. I will no longer work for any client that insists on hosting on GoDaddy. Some of their servers return non-standard values from basic calls such as $_SERVER['SCRIPT_NAME'] and they often cache the .htaccess and php.ini files so that changes you make don't take effect on the server for a while which makes troubleshooting these things damn near impossible.
IMHO, this has the potential to turn into a very long, very frustrating thread that will end with moving away from GoDaddy just like many threads have concluded in the recent past. As I say, search for 'GoDaddy problems' on these forums and you will see what I mean. It's almost always cheaper and faster to just cut your losses and move to a new host. I will no longer work for any client that insists on hosting on GoDaddy. Some of their servers return non-standard values from basic calls such as $_SERVER['SCRIPT_NAME'] and they often cache the .htaccess and php.ini files so that changes you make don't take effect on the server for a while which makes troubleshooting these things damn near impossible.
Had this a couple of times myself. Hutman's right, white screen usually indicates a php error. Error reporting's probably turned off. Add "error_reporting(E_ALL);" and "ini_set(" display_errors", 1):" in index.php before the require ("dispatcher.php ") statement but only if you can't find anything in the logs. You can empty the cache manually, go to the /files/cache folder and empty it. It's not going to be an URL rewriting issue, mod_rewrite is supported in every hosting package for as far as I know. Maybe an issue with a different php version.
Before you moved the site did you:
1) Clear the cache
2) Turn the cache off
3) Turn off Pretty URLs