multisite manager returning a "HTTP 404 - File not found"
| Project: | Multisite Manager |
| Version: | 6.x-1.0-alpha1 |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
We are in the middle of evaluating different CMS packages and we found that drupal seem to be worth looking at.
I followed the INSTALL.txt and still can't seem to get it to work. I am using the multisite_manager-6.x-1.0-alpha1.tar.gz download.
Our Drupal 6.8 is installed on the following path: /var/www/html/cms/drupal68 or
http://foo.edu/cms/drupal68/
Using the above information I tried to configure it this way(but its not working):
MY APACHE CONFIG:
<VirtualHost *:80>
AliasMatch ^\w+/(.*) /var/www/cms/drupal68/$1
DocumentRoot /var/www/cms/drupal68/
</VirtualHost>
2. MY ./sites/default/settings.php file
----CODE BEGIN-----
$requri = explode('/', request_uri());
if (sizeof($requri) >1 && $requri[1]=='site' && $requri[2] != '') {
$my_site_base = $requri[2];
#this will be the database shared between the main site and the shared sites
$db_url = 'mysql://foo_user:foo_pwd@localhost/database';
$db_prefix = $my_site_base."_";
$base_url = "http://foo.edu/$my_site_base"; // NO trailing slash!
}
----CODE END-------Example, I created a site called 'cse'. After submitting the form it happily goes and creates the Database and a link for the new site. However, when you click an the link provided you get HTTP 404 - File not found. error. And the path/url is http://foo.edu/cms/drupal68/site/cse
Can someone tell me what Am I doing wrong?
Right now the only thing that seem to be doing is creating the database for the newly created site.
Thank you.
#1
Do you have the following in .htaccess?
RewriteCond %{REQUEST_FILENAME} ^/var/www/cms/drupal68/site/.*RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^\w+(/)?(.*)$ index.php?q=$2 [L,QSA]
Have you tried adding index.php to the link it generates? I know that shouldn't make a difference, but it can.
#2
I'm having the same issue. I do not have clean url's enabled, as I understand they can cause some issues when using multi-site (it's not even imperative that this site have clean url's, so I'm happy with them turned off).
I used this module to add a new site and while it did create the content node without any problem, the subsequent link I'm given goes nowhere:
Original site: http://www.mysite.com
Link i'm presented with: http://www.mysite.com/site/newsiteshortname
Any ideas? This is a semi-new site and installation... I run drupal through this host (1and1) all the time with literally a dozen different client's websites with no problems. It seems odd that this would happen from just enabling the module and creating a new site node, which makes me think I've just got something configure poorly.
A thousand thanks to whoever can lead me in the right direction.
Edit: i'm running the most recent ver of drupal as of this post, 6.12, and all of my modules are up to date. (these are standard modules like views, cck, xmlsitemap, and a half dozen others. nothing funky)
#3
you need to make the symlink mentioned in the INSTALL file.
#4
Thanks. I am having trouble understanding that aspect, because in the installation instructions and on the drupal page for multi-sites, the URL for the new site is never actually given. When I first created a multi-site by hand (following the instructions on the drupal page) I was never told what the URL would be in order to visit this new site. I did a lot of Googling, too, and didn't come up with anything. I assumed that pointing my browser to www.example.com/sites/multi-site-name/ would work, but of course it didn't. The instructions about the symlink say to point my new domain to a folder pattern similar to this (although sometimes it uses the word "/site/foldername" and sometimes "/sites/foldername"). I don't understand how creating a symlink from a domain to a folder that returns error 404 will do anything useful. I am probably missing something simple but I read all of the documentation on the multi-site page and still haven't read a line saying what the new URL would be to get Drupal to generate the page content for the new multi-site.
#5
After taking another look at the INSTALL.txt file, I've run across this:
3. Any modules required for profile selections must be installed on
BOTH the main site's modules directory AND the subsidiary site module
directory (a symlink will do just fine);
the former in order to install, the latter in order to run.
Isn't it counter-intuitive to have modules installed in 2 directories? Doesn't that go against the whole point of multi-sites? I know someone knows the logic here so I hope they can share it with me and anyone else wondering.
#6
It may be counter-intuitive, but also useful, depending on which modules are in your profile, which ones you want to make accessible for installation by site owners, and what other sites you run from the same drupal core code, etc.
You can remove an redundancy by putting the modules in the sites/all directory that are required for the profiles.
The site's URL isn't listed anywhere, because it depends on how you configure mm, your htaccess file, etc.
If you make the symlink with `ln -s . site` run from your drupal core directory, then it will be with a /site/YOUR_SITE (note: not plural)
#7
This stil doesn't work for me. Same problem - the node is created but the clickable link gives me 404 Not Found.
File does not exist: /var/www/html/site
This directory obviously doesn't exist - so I'm confused how I'm supposed to access the site. Any ideas?
#8
Yea I'm still in the same place. It gives me a 404 error when sending me to example.com/site/mysite
At this point I'm willing to pay someone to help.
#9
I don't think this will ever work on my host (1and1) and so I've just got to give up. Looks like I will need an installation of Drupal and all modules for every site variant that I want.