Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
if FileConfig is enabled, you can do the same with a lot of Rewrite rules
(if you can get clean URLs working, then in theory, you could get this working)
I came up with some Rewrite rules that seem to be working within a .htaccess.
Try this after symlinking the drupal directory ./site -> . (copying the drupal dir into ./site should also work)
Well, the easiest thing is not to use '/sites/' because that's already a special directory for Drupal. Make it '/site/' and the symlink 'site'.
If you're set upon '/sites/' I'm not even sure if it's practical without Alias. The issue is that if you have modules that serve any content (javascript/css/image files) which is pretty common, then those files will be served from /sites/..../blah.css. If you're not really interested in separating core modules from sites modules, I suppose you could try moving all your modules and themes into the drupal root section ./modules and ./themes. If you ever get something working with a '/sites/' URL please post how you do it. My guess is it's a lot more work than it's worth.
wretched sinner...: It's probably better if you don't hijack other tickets. The other users on this ticket probably do not want email about your issue. Since this ticket, there are better .htaccess rules in the INSTALL file. have you tried those? Did you make the symlink? Did you set the /ABSOLUTE/PATH correctly? What did you set it to? If you're unable to fix this, please open a NEW ticket.
Comments
Comment #1
schuyler1d commentedif FileConfig is enabled, you can do the same with a lot of Rewrite rules
(if you can get clean URLs working, then in theory, you could get this working)
Comment #2
sharique commentedI'll try then get back to u.
Thanks
--
Sharique
Comment #3
schuyler1d commentedI came up with some Rewrite rules that seem to be working within a .htaccess.
Try this after symlinking the drupal directory ./site -> . (copying the drupal dir into ./site should also work)
Let me know if this works for you.
Comment #4
rtdean93 commentedPlease help me understand the symlink process.
i have created a symlink to my root directory for drupal. I have moved the symlink to the sites directory. What should I name the symlink?
Suppose my site URL is
www.mymainsite.com
and my multisite is...
www.mymainsite.com/sites/newsite
Given that - what should I name my symlink and where should I put it?
Also - the above rewrite rules - should they completely replace the default .htaccess file or be appended to the end of the default file?
Thanks for you help.
Comment #5
schuyler1d commentedWell, the easiest thing is not to use '/sites/' because that's already a special directory for Drupal. Make it '/site/' and the symlink 'site'.
If you're set upon '/sites/' I'm not even sure if it's practical without Alias. The issue is that if you have modules that serve any content (javascript/css/image files) which is pretty common, then those files will be served from /sites/..../blah.css. If you're not really interested in separating core modules from sites modules, I suppose you could try moving all your modules and themes into the drupal root section ./modules and ./themes. If you ever get something working with a '/sites/' URL please post how you do it. My guess is it's a lot more work than it's worth.
Comment #6
schuyler1d commentedComment #7
wretched sinner - saved by grace commentedI have tried this .htaccess file, but it breaks the clean urls on my existing site, so I can't setup a sub site to try this either...
Comment #8
schuyler1d commentedwretched sinner...: It's probably better if you don't hijack other tickets. The other users on this ticket probably do not want email about your issue. Since this ticket, there are better .htaccess rules in the INSTALL file. have you tried those? Did you make the symlink? Did you set the /ABSOLUTE/PATH correctly? What did you set it to? If you're unable to fix this, please open a NEW ticket.