Cached pages are created but not served

i have just found out that nevertheless i activated "Static page cache" option on /admin/settings/performance and set 1 hour as Minimum cache lifetime, it shows any submitted nodes on the first page immediately. or first page is not cached? anyway, none of other pages (not on the first page) does show <!-- Page cached by Boost at 2006-11-24 15:06:31 --> message in page source.

I saw this happen once, too. What I did was reset the Boost settings to the defaults (on the Site configuration -> Performance and Site configuration -> Performance -> Boost pages), disable Boost, re-enable and then reconfigure my Boost-related settings.

Please try this and change the issue to "fixed" if it works for you.

Simply disabling and re-enabling the module didn't fix it for me.... but deleting the cache files as well did the trick.

Thanks to all, finally got it working!

yngens, how did you solve this problem?

as was suggested above disabled, deleted cache and re-enabled. of course, the most important part besides this is to properly install the module.

Did what yngens suggested (disabled, deleted cache and re-enabled) but with no effect, the pages are still served throughout database although they are cached copies created on the fly by Boost module (I see those files on the server).

Me too :/

Disabled it, deleted everything under /cache, re-enabled and refreshed a page a coupla times but never saw the "cached by" comment.

Here's my .htaccess file in case it helps. (I have about 2 lines of stuff I added in myself)

Edit: Moved quoted .htaccess file into an attachment.

Seems to happen with 5.x-1.0 AND 5.x-1.x-dev.

Changing this to critical because it effectively makes the module unusable.

Got a working solution folks :)

The problem is that the .htaccess directives use the %{SERVER_NAME} variable ($_SERVER["SERVER_NAME"] in PHP) which is a value taken directly from your Apache configuration which, in the case of my web site (and czkuba's site) doesn't include the "www" bit.

So our cache files are being created under www.example.com/cache, but the .htaccess is testing for the existence of cached files under example.com/cache which it NEVER finds so the plain, un-cached version gets served up.

To fix this, I simply replaced all occurrences of %{SERVER_NAME} with my full domain name. I also enabled and edited the first commented rewrite rule that redirects requests for example.com to www.example.com. That should stop cache files from showing up in the wrong directory -- saving space.

Hope this helps someone else out there!

Thanks, norio! Excellent detective work.

Since you assigned this to yourself, would you be able to write this up for the Boost documentation and contact wulff or Arto?

  http://drupal.org/search/user/wulff
  http://drupal.org/search/user/Arto

This isn't "fixed" until the documentation is updated (in the INSTALL.txt, the comments in the .htaccess or on the project page) so I'm reopening it to make it easier for others to find this issue in the queue.

Happy to do that but never done it before so can I have a little guidance? I'd love to contribute more back to Drupal but I just don't know how.

norio, all you need to do is post a modified boosted.txt file that has the correct .htaccess rules and relevant comments and change the status to "needs review" (so it can be easily found and reviewed by others). At that point others will hopefully chime in and say whether the solution works for them or not. :)

In the end, only wulff and Arto have the ability to update the boosted.txt file in the next release or snapshot (check the "Developers" link on project pages to see a project's maintainers) and it's important for them to review it. I know bjaspan has been working a lot on Boost so maybe he can weigh in here, too.

Meanwhile, anyone can change the status of this issue to "needs work" (and offer some constructive feedback about your solution) or change it to "ready to be committed" (this is usually done by someone other than the person who offers the solution). Your detective work and solution both look sound to me, but I haven't tested it yet (I have an intermittent problem where Boost serves outdated CSS files so I've disabled it for now) so I can't change the status to RTBC.

Hopefully this response is helpful. It's probably too much but you did assign this issue to yourself. :P

Instead of editing the boosted.txt file, I've added new instructions to the INSTALL.txt file. I hope this will do!

By the way, Christefano, your problem could probably be solved by finding lines like this:

RewriteCond %{REQUEST_URI} !^/admin

And adding underneath them:

RewriteCond %{REQUEST_URI} !^.*\.css

Personally, I've enabled CSS file aggregating, and I'm using this line (instead of the above) to fix the CSS issue:

RewriteCond %{REQUEST_URI} !^/files/css

Seems to be working fine.

Seems like that css line should be in our boosted.txt file, no?

Sounds good to me. I recommend another similar line for .js files.

Hi everyone, i want to know how to let this module work with pathauto module?

Thanks, norio. I think that line ought to be rolled into the next release.

@norio - Thanks for the fix!

Symlinking the non-www cache directory to the www cache directory works too, and is a one command fix.

unix> ln -s www.wisebread.com wisebread.com

@snowwind - Boost should work with Pathauto out of the box. You don't need to do anything special.

I'm having the same problems that norio and yngens had - the cache is created but those cached pages aren't served.

I have tried the 'delete cache / deactivate / reactivate module' approach, and modified my .htaccess file to replace %{SERVER_NAME} with the domain name (thus making sure the path to the cache is correct), and I still can't get the cached pages to show up.

The only other difference to my .htaccess file compared to boosted.txt is that I have to use

RewriteBase /

..in order for my clean URLs to work.

I'm viewing pages which I know are cached in a different browser that has never been used to log in to Drupal, just to make sure, and no <!-- Page cached by Boost etc etc --> messages show up in the page source.

Any suggestions?

The issue is likely due to an error in the rewrite rules. Here is a patch, basically in the last two RewriteRule lines, change /$1 to /%{REQUEST_URI}

Thanks for that, I've tried making the changes it doesn't work! I'm really rather confused...

If I don't have RewriteBase / the whole (test) site breaks - I wonder if that can be the issue?

(I've done the usual browser reset to make sure uncached pages aren't in my local cache)

Any further pointers greatly appreciated - my site it likely to get a mention on TV this weekend, and could do with some super-cacheing..!

[Edit]

I'm now getting

Fatal error: Call to undefined function drupal_get_normal_path() in /home/s/a/sandbox/public_html/sites/all/modules/boost/boost.module on line 13

on my homepage (well, sandbox homepage) but other pages work fine. I'm stumped!

hi,
I have installed the boost in a sub directory called "whatever", I have tried all the suggestions above, still can't get the boost to work. Any suggestion? I did see the cached page were generated, just can't get the browser to point to the right location.

Attached patch is based on #23, and fixes the following:

- Use %{REQUEST_URI} instead of $1, since %{REQUEST_URI} has been tested, not $1.
- Move all %{REQUEST_URI} tests on a single line, and order them alphabetically.
- Add special paths "files" and "system" to %{REQUEST_URI} tests. Those shouldn't be tested for cached static pages.

#336166 is a duplicate of this issue.

I've tried both fixes and neither works. Boost generates the files within /cache, but they are not served.

Is there any way to debug this? How can I see what directory apache is pointing to? Perhaps my host doesn't have a standard setup.

I'm using hostgator BTW. If anyone has gotten boost working on a hostgator shared server, please let me know. Thanks.

My install is in a subdirectory "/drupal" and thus the above fixes don't apply.

The solution can be found here:

http://drupal.org/node/101147 , #9

Be sure to change "share" to whatever your subdirectory is named though.

I still can't get the cache pages to be served, even though I see them being created in the cache folder.

I've made some changes to the htaccess file as in the patch, and disabled Boost, deleted cache, then enabled it again under Performance. Still not working.

Can someone take a look at my htaccess file and tell me what else I could do to get it working? I really want to get it working!

Thanks in advance!

Weird, seems to work now. Not sure what I did to get it working, but now the message is being displayed in the source code.

:-D

Can you clarify the changes needed to the htaccess file if you're experiencing this bug?

For example, do you change

RewriteCond %{DOCUMENT_ROOT}/cache/%{SERVER_NAME}/0/index.html -f

to

RewriteCond %{DOCUMENT_ROOT}/cache/www.example.com/0/index.html -f

?

If so, I've made these changes, and Boost is not working for me, either - pages are getting created but not served. I'm NOT in a subdirectory.

Thanks!

Related to previous fix by norio (thanks for getting me up an running initially norio). However at the moment only the index page is being served. All other pages are coming from the database. I applied all fixes noted by norio. I have attached the .http file if anyone gets a moment to cast their eye over it.

Cheers

UPDATE: Please disregard - started again by copying and pasting boosted1.txt again and working through each modification.

Thanks again norio

Using 6.x-1.0-alpha1, only frontpage is loaded from static cache.

- static pages created with the correct domain (not install under subdirectory)
- replaced .htaccess (tried boosted1.txt, boosted2.txt and use domain directly, all same result)
- tried disabled and enabled boost, no changes (reverted .htaccess and redo from scratch)
- tried uninstall and reinstall boost, no changes (reverted .htaccess and redo from scratch)

So far only manage to load frontpage only.
Other pages are with path alias, does boost suppose to generate based on path alias, e.g. about.html or node/1.html? I'm getting the latter.

Any idea?

same here...

Same problem. I can see that static files are served for the frontpage, views pages but not for single nodes which have a path alias.
In the cache directory "node/31.html" is created although it should be "events/party.html" for ex.
If I query node/31 with the browser I see the static page but when using the path alias it's not working.

No GlobalRedirect Module enabled
Drupal 6
BlockCache enabled.

Please help us.

It seems that replacing $_GET['q'] with $_REQUEST['q'] makes aliased pages like "blog/20090303/today-was-good" work and the appropriate folders get created. It just doesn't work for the frontpage.
In the code I've seen a TODO bit about alias/symlink. Maybe that's the problem!?

I got it working with some patches from other threads. The essence is to change $_GET['q'] to $_REQUEST['q'] and excluding comment reply + search pages.

Here's my boost module (in text form)

You can see it in action at www.wahl.de

Yeah.. took me this whole day, but finally I got it working!
I'm using Drupal 6.10 in a subdirectory called drupal, on localhost (Apache/Windows).

First of all, after a normal installation of the module (using boost1.txt as .htaccess), I replaced boost.module by the one in #38 (http://drupal.org/node/204832#comment-1323186).
In Drupal I've set the caching directory to "cache/localhost".

Then, in .htaccess, I uncommented:
RewriteBase /drupal
and changed it to:
RewriteBase /drupal/

Then I changed the #BOOST-section of my .htaccess to the one in http://drupal.org/node/101147#comment-474871 and changed /share to /drupal.

It was still not working, so I replaced (in my case) %{SERVER_NAME} with localhost. Still no results....

Suddenly I saw "/0" everywhere, but that directory doesn't exist on my system! After I deleted all the /0's, it all worked!

Please leave a message if this helped you (or not)!

EDIT: I've tested on a 6.10 drupal in the root of the vhost - symlinks are created and boost (6.x.dev) works fine. No patches from here applied.

patch from comment #26 was against 5.x. It needs to be done against 6.x and boosted1.txt & boosted2.txt files.

re-rolled #26 for 6.x

Hi

I use boost on drupal 6.10

My drupal installation is in a subdirectory.
I use path module to rewrite the urls.

My problem : boost does cache the pages as nodes but not as rewrited urls.

For exemple, the page node/56 is rewrited as hello.html
Boost will cache only 56.html in /cache/mysite/node/56.html and not hello.html in /cache/mysite/hello.html

So when i load in my browser the node/56 the cached page will be served.
But when i load hello.html the page will be made and served by drupal without using the cached page at all.

How to solve that?

Mikey, your patch will lead to a 500 internal server error in my case.

Thanks for any help :)

@patataur
Which version of boost are you using? the latest 6.x dev might fix your first problem. Can you give more details on the 500 internal server error?

Hi Mickey

I'm using the 6x 1.0 alpha2 version and let you know of any improvements.

I will try with the latest dev version but am a bit afraid to use it on a production website.

I'm not at home now so cannot replicate the 500 internal error. But i suspect it is due to url rewriting getting messed up as i also managed to have a 500 server error while trying to get the correct url rewrite in the htaccess for some old pages that will not be ported in drupal. In this case it might be due to my having drupal in a subfolder of the production website putting it all together before switching the website to drupal "live".

Thank you for your fast answer :)

@patataur
Does clean URL's work on your site right now?

use cvs to checkout the dev cause the latest dev is generated with a little lag

Yes, clean URL are working right now and fine :)

everyone that has issues - please use the latest dev.tar.gz from the project page or even the latest CVS. Most of the issues go away if you do and we are still testing things and reluctant to release the next stable ...

NOTE: If boost doesn't crash your site (a very rare thing - I myself has not experienced a 500 error even though I am one of the main testers and patchers ) the worse thing that can happen is that your html_cache pages are not served at all - which wil just give the user what drupal woud normally serve... no big deal and no blank screen - not at all - never.

So I anticipate reports from people with the latest dev.tar.gz :
1. with drupal in root of the vhost
2. in a subdir

@ rsvelko and @ mikeytown2

Back at my workplace, i tried the dev version of boost.

It is now working perfectly.

For info again, my issue was that my rewrited pages (mysite.com/rewrited.html) were saved by boost as nodes (mysite.com/node/12) and thus when looking for the rewrited page drupal had to serve it as it had been saved in /cache/mysite/node/12.html and not in /cache/mysite/rewrited.html

Now this issue is solved in 6.x-1.x-dev

Thanks a lot!

pushing this back to needs review since patataur's issue was not related to this patch.

quote from #26:

- Move all %{REQUEST_URI} tests on a single line, and order them alphabetically.
- Add special paths "files" and "system" to %{REQUEST_URI} tests. Those shouldn't be tested for cached static pages.

these parts of the patch are easy and ok to commit.

- Use %{REQUEST_URI} instead of $1, since %{REQUEST_URI} has been tested, not $1.

someone see apache manual for REQUEST_URI and Rewritebase :
1. what can go wrong if we replace $1 with it (possibly miss some characters present in $1 and not in REQUEST_URI)
2. add to 1. the different settings for Rewritebase - commented out| / | /drupal | /drupal/

Maybe with Rewritebase / $1 has "/" in it while REQUEST_URI lacks '/' always - so that's why using $1 while REwritebase / causes trouble ...?

4 more dir's to add to the do not lookup rule would be
/misc
/modules
/sites
/themes
get rid of files since that's inside sites. Also fix the alphabetical listing. Proposed changes takes care of sites not using css/js aggregation.

Old

New

In terms of $1 vs %{REQUEST_URI} they seem interchangeable. Here's mongrel's wiki on static caching; they use both kinda haphazardly http://mongrel.rubyforge.org/wiki/Apache. But a trend that does show up is that %{REQUEST_URI} is used for RewriteCond and $1 is used for RewriteRule. Apaches documentation seems to agree with this http://httpd.apache.org/docs/2.2/misc/rewriteguide.html.

@sun
Could you explain your reasoning for using %{REQUEST_URI} in the RewriteRule part? Or does it even matter as long as it works (citing mongrel).

Hello,

It's good modules for drupal !!! But i have a little problem.

The cache is generated, but no use in the front for somes pages.

I have a page with this design /url/taxomony/taxomony/node

The is generated cache and push this in the Front OK
The /url/ is generated cache and push this in the Front OK
The /url/taxomony/ is generated cache and push this in the Front OK
The /url/taxomony/taxomony is generated cache and push this in the Front OK
The /url/taxomony/taxomony/node is generated cache and but no push this in the Front NOK

I have find the PB, because, the file/folder cache is not good.
I have :
/cache/site/url/taxo/taxo.html
/cache/site/node/{node_id}.html but i think the good is : /cache/site/taxonomy/taxonomy/{node_title}.html ???

No ?

Best regard,
(excuse me for my english, i speak french)
Sébastien

Try the latest dev, I think it might solve your problem.

To test and make sure boost is working, view the source of the page, when not logged in to your site. There should be a boost message at the bottom.

Can't seem to get Boost to work. Using latest dev version, tried both boost1 and boost2 for my .htaccess . Cleanurls work, pages are successfully generated in the cache directory, but inspecting the html shows the cache isn't being retrieved.

As a first step to debug-- I guess I should double check that I'm putting the .htaccess in the right place?

So, for example:

my http root is set to /home/username/public , such that http://www.example.com/test.html will load /home/username/public/test.html

My drupal is a subdir named drupal , /home/username/public/drupal

My cache dir is a subdir of that, /home/username/public/drupal/cache

The .htaccess file should go to the drupal directory, right? The same dir that has drupal's index.php? So in my case, /home/username/public/drupal/.htaccess ?

I'm assuming this is the case, since cleanurls work, but that's one potential source of error I considered.

Another potential source of error-- I'm not entirely what my RewriteBase should be. I've tried various values in a desperate attempt to get boost working, but no luck.

Any help _greatly_ appreciate. Majorly good work to the person(s) behind this module. Rewrite rules are voodoo, and not for the faint of heart. :)

.htaccess file should go in the subdir

Try these rules for subdir install
http://drupal.org/node/101147#comment-474871

wrong link, follow these directions
http://drupal.org/node/101147#comment-1496406

mikey, thank you so much! The links you provided didn't exactly work as-is, but they were close enough that I managed to find success. Page loads dropped to 1/10th what the used to be! Thank you thank you thank you!

Using 6.x.1.x-dev, with my drupal directory at http://www.example.com/drupal , I found success using the following .htaccess rewrite rules:

Replacing $1 (which references back to (.*)) with %{REQUEST_URI} is the smart thing to do as sun has pointed out. Combining the 3 dir's into 1 and adding some others looks like this (new)

And adding this to the top of the boost section for performance reasons

$_GET['q'] has been replaced with $_REQUEST['q'], so that part of this issue is done. I'm marking this RTBC, since the above rules have been tested IMHO. Once these & other changes go in, updating the subdir & multi-site instructions should be the next priority for the htaccess rules.

committed

Automatically closed -- issue fixed for 2 weeks with no activity.

Everytime I try to enable the Boost Module and I click save I see a blank page and this error in the logs:

PHP Fatal error: Call to undefined function drupal_install_schema() in /home/webserver/html/modules/boost/boost.install on line 41, referer: http://localhost/admin/build/modules/list/confirm

function boost_install() {
// Ensure that the module is loaded early in the bootstrap:
db_query("UPDATE {system} SET weight = -90 WHERE name = '%s'", 'boost');
// Create tables.
drupal_install_schema('boost'); ##<--- this is line 41
}

anybody knows how can I fix this error?

@wordgeist
Umm... thats not a good error to have. Are you running a hacked version of core?
http://api.drupal.org/api/function/drupal_install_schema/6

Also open a new issue next time.

Re-Closing

open back up for 5.x starting with #26.

I'm using the version of drupal (drigg)

@wordgeist
That's a core function... I can not help you if it's not there. It's not a boost problem if your missing a core function.

Please create a new issue next time, like I asked you before.