Boost .htaccess disables multisite install
| Project: | Boost |
| Version: | 5.x-1.0 |
| Component: | Apache integration |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Running Boost on 5.7 install with two sites, exampleA.com and exampleB.com on the same server using WHM/CPanel domain parking to enable the drupal multi-site install. ExampleA.com is the primary domain and the name of the DNS server is ns1.exampleA.com.
The multisite works fine until the new .htaccess file for Boost is installed in the root level of exampleA.com. Boost works great, begins caching pages for exampleA.com. But when I type exampleB.com into the address bar, the index page for exampleA.com comes up. The only way that I can get into ExampleB.com is to type exampleB.com/node or exampleB.com/user into the address bar. Still. when I click any "Back to Home" link on exampleB.com I'm taken to the home page of exampleA.com.
To recreate do this on your own site:
Install Boost on exampleA.com
Install .htaccess file
Go to exampleA.com
Go to exampleB.com
Would it help to install the .htaccess file in the sites/exampleA.com and sites/exampleB.com folders instead of the root folder?
Server specs: Linux, Apache 1.3.39 (Unix), PHP 5.2.0, Mysql 4.1.22-standard, cPanel X v2.6.0.
#1
I am interested in this too.
Following.
#2
subscribe
#3
Replacing instances of %{SERVER_NAME} with %{HTTP_HOST} solved this issue for me.
#4
Attached is a patch that implements the comment in #3
#5
Hi
Thanks for the patch, but when i apply it, i get the following error:
Fatal error: Call to undefined function drupal_get_normal_path() in /home/virtual/drupal5c.com/sites/all/modules/cache/boost/boost.module on line 13#6
A cheap guess, but why do you have the boost folder in a folder called cache?
#7
We have the modules divided into folders, admin modules, cache modules, and so on.
We have a multisite install with *some* modules, and this way is more manageable.
Do you mean that this can produce problems?
#8
Anyone can provide a clue to fix this?
Thanks!!
#9
Subscribing
#10
Also interested. Thanks.
#11
#3 has to do with the rewrite rules you place in your .htaccess file. Also #454652: Looking for a co-maintainer - 5.x.
#12
#5 - are you running a special homepage (front module) or something like that? I'm getting the same error and wonder if its that module. It's also an int'l site.
#13
It has been a while, but nope, I was not using front module or nothing *strange* for homepage.