By labourstart on

I'm working with a new client who's set up Drupal themselves on a shared host on a commercial server. I was about to upgrade them to Drupal 6.13 and was backing up their files via FTP but kept having problems. When this has happened in the past, I've always used chmod to make the files readable/writeable (usually it's files in the sites/files directory). When I completed this, Drupal threw up '500' error messages and the error log has only this:

Premature end of script headers: /home/halldj/public_html/drupal/index.php

I'm assuming it's a pemissions issue, so I've looked through the permissions for many of the files on the new site and compared them to one of the many other Drupal sites I maintain and I can't find the difference. I've tried doing chmod 777 to nearly everything - still not working.

Any ideas? Thanks.

⋅ Categories: Drupal 6.x

Comments

drooppi’s picture

drooppi commented

Depending on what FTP client you used,
sometimes the hidden .htacess file in the drupal root
directory is not copied.
On *nix/Linux a file name starting with a dot is a hidden file. If you have your settings in your FTP program to not show hidden files and you go CTRL-A (to select all files in the folder), you will usually miss the .htaccess.

Without it, you can get http 500 (server error) messages.

So make sure you copy it too when backing up the drupal files / drupal directory.

labourstart’s picture

labourstart commented

Any other ideas?

Thanks.

labourstart’s picture

labourstart commented

Some of the PHP files were writeable by group or all -- once I changed this, it was OK.