Hello all,

I ran a very successful drupal guild site for a while now. When the payed hosting plan ends, I will have to move to a new server I just bought.

So... what I'm trying to do here is to migrate from one server to another. I have overcome a lot of problems (database mostly) but i seem to get stuck at one point.

Version I'm using in both cases is 4.7.0.

My checklist:

-> Install VHCS + Apache in Debian Sarge Server: Done.
-> Backup Site and Database at old Hosting Provider: Done.
-> Flush the database into the new Server: Done.
-> Install Drupal in the new Server: Done.
-> Get the theme and the addons into the new installation: Done.
-> Navigate the webpage: Stuck.
-> Update Drupal: Pending.
-> Change DNS pointers: Pending.

The first page looks exactly the old one (theme, text, blocks, even event :)). The thing is, when I click on any link the page reloads itself instead of following it. Login has the same behaviour too.

I have tryed to edit settings.php for the "base address thingy", but had no effect.

Any help would be appreaciatted.
Thank you in advance.

Comments

amen’s picture

i forgot to specify that when i installed drupal, the other drupal's database was standing in the place of a fresh one.

vm’s picture

did you flush the cache table ?

amen’s picture

just double checked it now - and yes, i did.

mfer’s picture

Do you have an unmodified .htaccess file loaded? Can you get to the login page via http://yoursite.com/?q=user/login?

amen’s picture

the .htaccess file is the same that came with drupal tarball. and accessing http://yoursite.com/?q=user/login has the same effect as every other thing. it just reloads the page.

cog.rusty’s picture

I guess that you also checked that the name of the directory under /sites containing the settings.php file is ok...

What PHP version? I am asking for ruling out a PHP 5.2 bug issue.

amen’s picture

it's solved :) most of it anyway :P

disabling clean urls in settings.php together with upgrading to the current drupal solved it.

Now I'm having the same problem... but it's only happening in administer >> modules, which is far less of a hassle.

Thanks a lot anyway!