Hi all
I am migrating my site to a new domain name. I loaded public_html and moodledata and changed the config.php to the new url.
Still site not working . Is there anything I missed out.
http error 500
Migrations could be to a new server ... thus new environment. Is that what you are doing? or are you just changing the domain name?
One had to transfer the contents of public_html (the moodle code) and moodledata + moodledb sql dump imported). If you transferred code and moodledata ... if you used FTP to transfer, did you use binary mode in FTP?
Changing the domain name (FQDN) would also mean two other steps ... 1. the config.php file edits and 2. search and replace in the database for http://olddomain/ replace with http://newdomain/
Version 1.9.x did not have an admin tool to do the FQDN conversions in the DB. That had to be accomplished by editing the SQL dump of old site DB and doing a search and replace on the SQL dump file, before importing into the new database on the new environment.
Make sure you edit the config.php file with a text editor ... not word or any other word processor. There could be machine language symbols/characters in your config.php file that you do not see that's causing error 500's.
And last, but not least, the clip you've shown of your config.php file ... ** make sure ** there are no additional blank lines after the closing php tag in that file.
Unless I just totally mis-read .... :|
'SoS', Ken
Error 500's don't show much via web but your servers error logs will provide some clues. Could we see a clip of what some of those error log line say?
Also, to get more info from moodle (if possible), Section 7 of config-dist.php shows how to turn on debugging by adding debug lines to the config.php file.
Add those lines and let's see what moodle might saying.
Also, is this line:
$CFG->wwwroot = 'http://mysite/courses';
in your config exactly as you shared here ... or are you hiding your server's URL? Hiding ok here in forums as long as 'mysite' represents a fully qualified domain name of server that can be resolved via DNS.
It won't hurt to mention versions of Moodle involved ... found by looking at version.php file at the moodle code root.
'SoS', Ken