Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Kayin on
I'm fairly new to the CMS scene so please bare with me. I'm a little stuck. I'm moving a site that has been on drupal now for quite a while to another host. I want all the content to remain the same, I just want to transfer everything.
I copied the entire web directory over to the new host
exported the database off the old, imported onto the new
went through the config files and changed everything to the new database usernames and passwords
ultimately, the main page works like a charm, the files and images work, but as you can guess the pages themselves don't seem to exist.
Help?
-K
Comments
Give us a url and also
Give us a url and also explain,
.....the pages themselves don't seem to exist.
Are you getting white page, error pages, etc..?
Have you FTP'd and checked the directory and file permissions?
What version of mysql, php, apache (or OS) Plesk, RHEL3, FC2, FC3, FC4 ???
...and finally when you transferred your files are you sure you transferred your .htaccess file. Sometimes that is not copied depending on the host and/or config of your FTP app. To see all files set the file mask in your FTP app to -al if you cannnot see your .htaccess or other . files.
Traveling far and wide extends ones - self....
As in a mule traveling to the end of the field only returning as a mule, and not a horse.
Did you turn-off non-core
Did you turn-off non-core modules before you backed-up the database?
Were you logged-in or out of Drupal when you backed-up the database?
What do you see if you go to, for example, yoursite.com/node/2?
htaccess file
Do you have clean URLs turned on?
I've had problems like this when I didn't properly copy the .htaccess file. Check the existance and contents of this file. If it's correct, check that the host allows you to use .htaccess files.
---
Work: BioRAFT
When I say the pages don't
When I say the pages don't exist, I mean a big fat 404 page, no theme, no drupal, nothin but a big ugly apache default 404.
I didn't touch drupal when backing up the database or transferring. I didn't login to the drupal system to do a thing. I'm not even sure where the admin login is (let me guess, the obvious login in the corner right?)
I did check the system specs however to make sure it was compatible with drupal:
Operating system Linux
Kernel version 2.6.9-34.106.unsupportedsmp
Apache version 1.3.34 (Unix)
PERL version 5.8.7
PHP version 4.4.1
MySQL version 4.1.14-standard-log
The webhost that I'm using actually provides a little drupal installer to make it all nice for me. I didn't use it since all I was doing was copying the web directory and database.
Sorry for bein noobish, this is the first time playing with drupal. Another thing, the client doesn't want me giving out its address so I can't let you all look, not much too look at really though lol.
When I go to domain/node/2 or /node anything I get a 404. I can go to files and images, but nothing else
oops, and yes I did grab the .htaccess :)
-K
contents of .htaccess
Check the contents of .htaccss! i've been bit numerous times by this on a cPanel-based host because when I extracted the tar or FTP'd to make a test/backup site, the existing zero-length .htaccess file did not get overwritten.
As a test, I just deleted the contents of .htaccess on a test site i'm playing with. I now get Apache 404s on everything except the home page.
---
Work: BioRAFT
ah ha
ah ha! sneaky little webhost not transferring it.
Yea, that got it. Thanks man.
Next problem lol
Now when I try to go to a node it is repeating the domain over and over
for example:
www.ipaddress.com/~uname/~uname/~uname/~uname/~uname/~uname/ etc etc...
I'm connecting via ipaddress and not domain because the domain hasn't been transferred yet.
Do you think its the ~ screwing up the parser?
-K
It's a common problem with
It's a common problem with temporary URLs.
As I understand it, clean urls won't work because the temp url already uses mod_rewrite. Something like that, anyway!
I - and I know a few others - had a very similar problem, but it was sorted once the full URL was live.
Of course, all of that affects the database settings that you will have entered.