%{DOCUMENT_ROOT} not set correctly on Mosso hosting.

(Sorry, by 'this thread' I meant #428942: AHAH update textarea for .htaccess rules on performance >> boost page..)

Great - things work fine again after copying the suggested code from /admin/settings/performance to .htaccess. It was just a question of documentation, it appears. Thanks, this is an amazing module!

Hi again --

So things worked fine on a standard LAMP install on CentOS 5, but on my sites hosted at Mosso I still cannot get beta1 to work with the new .htaccess.

To explain, also in the previous version of .htaccess (alpha versions), I had to adapt the .htaccess to run at Mosso. Specifically, I had to use absolute path like this:
%{DOCUMENT_ROOT}/cache/
to
/mnt/path-to-my-site/web/content/cache/

Now, in the new code, I've tried without any change, and then with this change, but pages are not being saved (cache folder remains empty).

Maybe in the new .htaccess I have to do other modifications to get it running on Mosso? Any suggestions, things to try?

Works with the above change also on Mosso when using the latest dev release. Thanks!

@mikeytown2 re: #6 - tried to use the generated code in beta2 in my .htaccess on Mosso as you asked. Cleared all cache at /admin/settings/performance, then browsed anonymously and refreshed /admin/settings/performance The count of cached pages kept increasing there BUT on the anonymous pages, no matter how many times I cleared browser cache and tried different browsers, I am not getting the footer info in page source about the page being cached! For example this page - when I look at it logged in, the Boost status block tells me it is cached. But when I look at its source (give it a try!) it does not have the footer that would confirm it. (FYI, the setting to not cache on error is off.)

Please advise.. I am now not sure whether pages are served from cache. I leave this for some time for you to check but if not solved I'll get back to the old .htaccess code I know works for me (from beta1 and with #4 fix). Thanks for having a look at this.

@capellic -- thanks for your message.

(1) I confirm the cache dir is getting filled with pages.

(2) Well, you are repeating what I said in post #4 above and which you yourself used in #8. :-)
The idea is not to have to do this manual change on Mosso (or other similar) servers. mikeytown2 in #6 suggested a patch which I did not use, but I did use beta 2. In #9 I reported that without changing %{DOCUMENT_ROOT} I seem to be using cached versions (boost block says, and the anonymous pages seem fast) but that there was no confirmation in the source footer.

To this, I am hoping for an answer from mikeytown2. At this moment I am still running the beta 2 generated .htaccess and the footer does not show. Hope mikeytown2 can have a look and ask me for further info if needed. I would like to get this solved rather than give up and live with the need for manual changes.

All right; did that. See the transcript below. They recommend using %{PHP_DOCUMENT_ROOT}. I confirm that that variable correctly renders the path in Mosso. mikeytown2, is this something you can work into the module expecting it will work on all systems? Or can the module detect being on such a system and use %{PHP_DOCUMENT_ROOT} under some conditions? Hoping for a generic fix.

Tomas Fulopp: OK, working with Drupal community on an issue that is affecting websites installed on Mosso.
Tomas Fulopp: The problem is that a module sets .htaccess rewrite rules that rely on %{DOCUMENT_ROOT}
Tomas Fulopp: On all other known servers tested this variable provides path to the, well, document root.
Tomas Fulopp: In my case it is /mnt/path-to-my-site/web/content/
Tomas Fulopp: But that does not work.
Tomas Fulopp: Another user confirms this finding at http://drupal.org/node/482000#comment-1825828
Miguel S.: yeah, document root won't provide the valid document root path, it's best to use php document root, you can override that though so it always provides the path you need.
Tomas Fulopp: I've spoken with the developer of the module and I would like you to have a careful look at his response at http://drupal.org/node/482000#comment-1839464
Tomas Fulopp: What exactly should we use instead of %{DOCUMENT_ROOT} ?
Miguel S.: one minute.
Tomas Fulopp: Sure, take your time. Note we need a solution for .htaccess - PHP does not come into play in that case.
Miguel S.: i know, i just want to confirm it.
Tomas Fulopp: Thx.
Miguel S.: it should be: %{PHP_DOCUMENT_ROOT }
Miguel S.: If you take a look at the data from a phpinfo(); you'll see that DOCUMENT_ROOT points to /var/www/html where as PHP_DOCUMENT_ROOT will point to the correct server address.
Tomas Fulopp: All right, we'll try that. Thanks a lot.
Miguel S.: You're welcome.

OK, great; looking forward!

In order for me to understand: do you plan to add some kind of checkbox saying "generate .htaccess paths using php_document_root instead of document_root" or suchlike? Or are you able to detect the correct one for the given system?

Well.. not out of the woods yet.

I tried replacing %{DOCUMENT_ROOT} by %{PHP_DOCUMENT_ROOT} in the generated .htaccess, but despite running cron, flushing the tested page, trying different browsers with flushed caches, the boost footer did not appear in the source!

When I look at phpinfo() there is a section headed "Apache Environment" and one of the lines indeed is:
PHP_DOCUMENT_ROOT /mnt/path-to-my-site/web/content
(btw, there is also: REDIRECT_PHP_DOCUMENT_ROOT /mnt/path-to-my-site/web/content)

Which is the correct path.

Then I went in and replaced %{PHP_DOCUMENT_ROOT} in the .htaccess by that /mnt/path-to-my-site/web/content. Flushed and... the footer appeared in page source!

Any idea why is this... seems like the variable is set but it cannot be invoked by %{PHP_DOCUMENT_ROOT}? How then?

Re #19. Did that. No match for 'getcwd' :-(

Interestingly, FYI, in that array there are three mentions of that full path of mine (/mnt/path-to-my-site/web/content), namely in:
["REDIRECT_PHP_DOCUMENT_ROOT"]
["PHP_DOCUMENT_ROOT"]
but also
["DOCUMENT_ROOT"]

mikeytown2! It works!

#20 did it -- I used %{ENV:PHP_DOCUMENT_ROOT}, then actually deleted the cache dir and created a new one, flushed Boost cache in Performance, flushed browser caches... one try, no footer (normal), reload, and the footer is there, consistently, on any page I try!

Do you think you could roll this into the dev version so that I can try it that way?

It would be good if capellic could try it as well, but I am pretty sure it's a solution.

@mikeytown2 re #22 ... in case you still need to know that for some reason: there is no difference, they are precisely the same (slashes and all).

We're very close but not there yet...

The generated .htaccess is headed by:

Document Root:
* %{DOCUMENT_ROOT}
  /mnt/path-to-my-site/web/content
Value of %{DOCUMENT_ROOT} is recommened for this server.

So the path to my web directory is correct, but the problem is that it is not automatically selected (and the recommendation is incorrect), so the .htaccess code still uses %{DOCUMENT_ROOT}. (Could this be because this is not a new install? I did however run update.php after installing the dev. Or what can be the problem?)

Let me know how can I help.

(Edit: Note that if I set the second option, apply, and then use the resulting .htaccess code, Boost works OK on Mosso!)

See #24... There was no match for 'getcwd' in the $_SERVER array.

Your code returns ( precise path censored, as always :-) the following:

Array
      [%{DOCUMENT_ROOT}] => %{DOCUMENT_ROOT}
      [/mnt/path-to-my-site/web/content] => /mnt/path-to-my-site/web/content
      [%{ENV:REDIRECT_PHP_DOCUMENT_ROOT}] => %{ENV:REDIRECT_PHP_DOCUMENT_ROOT}
      [%{ENV:PHP_DOCUMENT_ROOT}] => %{ENV:PHP_DOCUMENT_ROOT}
      [%{ENV:SCRIPT_FILENAME}] => %{ENV:SCRIPT_FILENAME}
      [%{ENV:DOCUMENT_ROOT}] => %{ENV:DOCUMENT_ROOT}
Value of %{DOCUMENT_ROOT} is recommened for this server.

boost_print_r was producing array, so I changed it to var_dump($options) etc.

array(6) {
  ["%{DOCUMENT_ROOT}"]=>
  string(16) "%{DOCUMENT_ROOT}"
  ["/mnt/path-to-my-site/web/content"]=>
  string(56) "/mnt/path-to-my-site/web/content"
  ["%{ENV:REDIRECT_PHP_DOCUMENT_ROOT}"]=>
  string(56) "/mnt/path-to-my-site/web/content"
  ["%{ENV:PHP_DOCUMENT_ROOT}"]=>
  string(56) "/mnt/path-to-my-site/web/content"
  ["%{ENV:SCRIPT_FILENAME}"]=>
  string(66) "/mnt/path-to-my-site/web/content/index.php"
  ["%{ENV:DOCUMENT_ROOT}"]=>
  string(56) "/mnt/path-to-my-site/web/content"
}
<br />Value of %{DOCUMENT_ROOT} is recommened for this server.<br />/mnt/path-to-my-site/web/content<br />/mnt/path-to-my-site/web/content<br />

No, I get only %{DOCUMENT_ROOT} and the correct path, but not %{ENV:PHP_DOCUMENT_ROOT} as an option (see #27).

:-{

I wanted to report on this, so I uninstalled Boost completely, then installed the newest dev.

Got a wholly new problem: these two error messages after enabling the module:

* user warning: Key column 'mime_type' doesn't exist in table query: CREATE TABLE boost_cache ( `filename` VARCHAR(255) NOT NULL DEFAULT '', `base_dir` VARCHAR(128) NOT NULL DEFAULT '', `expire` INT unsigned NOT NULL DEFAULT 0, `lifetime` INT NOT NULL DEFAULT -1, `push` SMALLINT NOT NULL DEFAULT -1, `page_callback` VARCHAR(255) NOT NULL DEFAULT '', `page_arguments` VARCHAR(255) NOT NULL DEFAULT '', `page_id` INT unsigned NOT NULL DEFAULT 0, `extension` VARCHAR(8) NOT NULL DEFAULT '', `timer` INT unsigned NOT NULL DEFAULT 0, `timer_average` FLOAT NOT NULL DEFAULT 0, PRIMARY KEY (filename), INDEX expire (expire), INDEX push (push), INDEX base_dir (base_dir), INDEX page_id (page_id), INDEX timer (timer), INDEX timer_average (timer_average), INDEX page_callback (page_callback), INDEX page_arguments (page_arguments), INDEX mime_type (mime_type) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /mnt/path-to-my-site/web/content/includes/database.inc on line 517.
* user warning: Key column 'mime_type' doesn't exist in table query: CREATE TABLE boost_cache_settings ( `csid` INT unsigned NOT NULL auto_increment, `base_dir` VARCHAR(128) NOT NULL DEFAULT '', `page_callback` VARCHAR(255) NOT NULL DEFAULT '', `page_arguments` VARCHAR(255) NOT NULL DEFAULT '0', `page_id` INT unsigned NOT NULL DEFAULT 0, `extension` VARCHAR(8) NOT NULL DEFAULT '', `lifetime` INT NOT NULL DEFAULT -1, `push` SMALLINT NOT NULL DEFAULT -1, PRIMARY KEY (csid), INDEX page_callback (page_callback), INDEX page_arguments (page_arguments), INDEX base_dir (base_dir), INDEX page_id (page_id), INDEX mime_type (mime_type) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /mnt/path-to-my-site/web/content/includes/database.inc on line 517.

Then I went to the performance settings, and got another warning:
user warning: Table 'mydatabase.boost_cache' doesn't exist query: SELECT COUNT(*) FROM boost_cache in /mnt/path-to-my-site/web/content/sites/all/modules/boost/boost.admin.inc on line 534.
Did run update.php - no improvement.

Eventually went back to beta2 and ran update.php, which finally installed the missing tables.

FYI: as for the document root settings, there still are the two items:

%{DOCUMENT_ROOT}
/mnt/path-to-my-site/web/content

of which the second is my correct path, but it is NOT selected.

So - I think the Mosso issue is now satisfactory (even though not automatic), but the db install problems in dev are grave and do need attention (therefore marking this as a critical bug).

OK, went again through the whole disable > uninstall > enable > configure procedure -- the problem described in #36 is fixed, excellent, yay!