By Artaud on

Hi,

I am trying to install drupal 5.1 in a multisite configuration and I am encoutering the followint problem.
I have uploaded drupal files to the root of my site. Have created 2 folders with the names corresponding with my 2 sites in the folder "sites" and copied settings.php to both folders.

I then tried to open the base url of my site through the browser, expecting drupals "Database Configuration" page as is explained in the installation instuctions, however I am getting for both urls 500 internal server error page.

I remember getting this error message also previously with the installation of drupal 4.7, the problem then was the htaccess file. So I look for it in drupal 5.1, however there is no htaccess file among the files of drupal. Have I downloaded a currupt version of drupal or is there an other explanation?

Please, if someone have any suggestions it would be great. I have been muddling for hours now and doesn't seem to be getting anywhere.
Thanks!

⋅ Categories: Drupal 5.x

Comments

cog.rusty’s picture

cog.rusty commented

A .htaccess file does exist in Drupal's distribution.

It is possible that it has been uploaded but your FTP program does not show it because files starting with a dot are considered "hidden". FTP programs often have a "show hidden files" setting. (In Filezilla it is in "View > Show hidden files".) So you can delete it or rename it to see if that was the problem.

Of course then you won't have Clean URLs.

Artaud’s picture

Artaud commented

For some reason the .htaccess does not display both in windows explorer and ws-ftp, finally i was able to find it both locally and on the server. I now got rid of the 500 internal server error, but getting the multisite installation working is jet an other matter.

Well, I try and research some more, at the moment I am to confused to even formulate the problem in the form of a question.

Thanks anyway!

cog.rusty’s picture

cog.rusty commented

Just in case this helps formulate the question, the big picture is:

1. On the server side: Make all the domains point to the same directory where Drupal is installed. This can be achieved either with domain pointers, or with apache vhosts, or with Linux symlinks, or with Windows junctions.

2. On Drupal's side: With (1), any request for a site will cause Drupal's index.php to run, to check the requested URL and compare it with the directory names under /sites, and to serve the proper site.

The error messages are often good guidance if anything is missing (well... except error 500 which means "something bad happened with the server but I have no idea what").

Artaud’s picture

Artaud commented

Thanks CogRusty!
Your big picture is very helpful, I don't konw how to solve it yet but think I am starting to get an idea what might be the problem. I will put the question in a new post.

Thanks again!

fk’s picture

fk commented

Hi,
I am not the person who asked the question above, and i have been looking for 3 days for an answer to an issue I encountered. Your two points above helped me solve the problem in seconds. Thank you.