By grvgl on

I have copied the settings.php from sites/mysite.com/settings.php to sites/mysite.com.folder/settings.php. I am getting the error posted on http://drupal.org/node/417236.

Then, I contacted my hosting provider. My hosting provider has suggested redirect instead of symlink but that also gives the page not found error. I am confused what needs to be done?

Thanks,
Gaurav Goel

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

you can also set your doc root for mysite.com.folder to point to your base installation. Sometimes this can be done in the host panel, other times you have to have the host do it for you.

I've never used symlinks but I only use multisites to create a dev.mymaindomain.com instance allowing me to have a dev version of a site as a subdomain of a production site.

Information that would be helpful in your situation:

Is mysite.com.folder a live site? is it on the same server? under the same account? is it a subdomain or a totally different domain?

grvgl’s picture

grvgl commented

mysite.com is a live site and I am trying to create http://www.mysite.com/folder and everything is on the same server and under the same account. I have not created a subdomain, it will be a site with some different modules at mysite.com/folder.

By default mysite.com.folder points to public_html/folder. I do not know how the URL mysite.com/folder will point to sites/mysite.com.folder? I believe I need to do this to use the same Drupal code base of mysite.com for mysite.com/folder.

I am trying to create mymaindomain.com/dev instead of dev.mymaindomain.com. But where do you keep your settings.php for dev.mymaindomain.com? May be that will help me understand.

vm’s picture

vm commented

my settings.php for dev.mysite.com is typically from a fresh download of drupal core. where i take default.settings.php and rename it settings.php

a new unaltered settings.php is needed to allow the second instance of drupal install to run.

I don't know what you are going to do with a drupal install in your public_root and trying to install an instance in a subdirectory. When I use subdomains, I don't put the main install in public_root.

drupal tends to take over paths in subdirectories within it's own folder structure therefore it is taking over yoursite.com/dev which explains the page not found error.

grvgl’s picture

grvgl commented

Thanks for helping me and your patience to understand my problem.

I have only one install of Drupal and I want to keep only one. I am trying to make available a Flex interface at mysite.com/folder for the selected content from the main site mysite.com. So sites/mysite.com.folder/modules will have its own set of modules (swf files).

I am doing this in a subdirectory to avoid any problems with the main mysite.com.

(As per your response I think it is a good practice to install Drupal in public_root/drupal so I will do that).