A couple basic things that have caught me out before:
1. the base url in settings.php - try either changing it or commenting it out
2. if you're using clean urls, they often won't work on the temporary url given by a new host (i.e. ~username), so things could be messed up until you've transferred the domain if you've not already done that.
Nat
Nat,
Thanks for the information . I have been wondering if this was related to clean URLs. I may go to back my production host, turn off clean urls, export the database, import it onto the new server and try again.
Will let you know how it goes.
_____
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nathaniel Catchpole Sent: Monday, December 04, 2006 11:17 AM To: support@drupal.org Subject: Re: [support] Problems after move to new host
A couple basic things that have caught me out before:
1. the base url in settings.php - try either changing it or commenting it out
2. if you're using clean urls, they often won't work on the temporary url given by a new host (i.e. ~username), so things could be messed up until you've transferred the domain if you've not already done that.
Nat
It is generally recommended to clear the cache and disable clean URLs before moving a site. If you're running 4.6, then the $base_url is *required*, and should be the web path to the directory where your Drupal's index.php file resides. ($base_url became optional in Drupal 4.7.)
Drupal also works fine in a subdirectory that has a ~. I do it all the time on my home test system.
On Monday 04 December 2006 12:57, Larry Hedrick wrote:
Nat,
Thanks for the information . I have been wondering if this was related to clean URLs. I may go to back my production host, turn off clean urls, export the database, import it onto the new server and try again.
Will let you know how it goes.
-
Larry Garfield -
Larry Hedrick -
Nathaniel Catchpole