I've used Boost several times before so I'm experienced with setting it up, but this time I'm pretty clueless so I'm in need of help. Here goes:

My problem is that Boost won't generate files in the cache folder. It's not a new Drupal install (it's an existing site) and I have Boost functional on other sites on the same server. Being an existing site means that I can't provide exact steps to reproduce either. I've gone through the list at https://drupal.org/node/1459690 and triple checked them, and have also read everything on https://drupal.org/node/1434362.

Some of the things that I've checked are:

  • Proper folder permissions
  • Cache interference (I've triple checked that Drupal cache is off)
  • Disabled basically all other modules on the site except for some core stuff and field collection, entity API etc. (there are some fields that prevent med from disabling them) in order to make sure that no other module is interfering
  • Tried with/without "RewriteBase /". On one occasion the front page was created by boost as "_.html" which is correct, but it only happend once, and I was never able to reproduce it, and only seemed to work for the front page
  • Used Boost debugging (no errors in the logs, it just logs the arrays)

Additional information:
Drupal core version: 7.20
Installed modules on the site are here

I'm pretty clueless right now, so I'm hoping that someone has a bright idea that I haven't already tried... Thanks :)

Comments

adamgerthel’s picture

adamgerthel commented
Issue summary: View changes

added mre info

adamgerthel’s picture

adamgerthel commented
Issue summary: View changes

more info

Anonymous’s picture

Anonymous (not verified) commented

First thing that I would discount would be the existence of a DRUPAL_UID cookie which is the most frequent cause of boost being disabled. Some modules initiate a session for even anon users that just throws boost out.

The second thing that I would discount is an ownership/ php SuExec problem, by looking through the apache/ php fastcgi etc logs just in case it's configured to only write to certain permissions.

Next thing I'd check is that php session settings which changed from php 5.4 to 5.3 and I know that there have been reports that removing ini settings from the main drupal .htaccess file has suddenly caused boost to start working (though no-one has been able to pinpoint which one).

Another possibility may be on a very locked down server running Selinux policies where a custom policy would have to be introduce to allow the webserver to write to a previously unknown folder, this is rare but I have seen it before and would require looking up restorecon -R and chcon -R.

Anonymous’s picture

Anonymous (not verified) commented

Another thing worth checking on other people's installs, is that the .htaccess file is being read for the rewrite rules and that nobody has put

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^ index.php [L]

In the virtual host configuration.

adamgerthel’s picture

adamgerthel commented
Status: Active » Closed (fixed)

Thank you! We had

ini_set('max_execution_time', 10800);

In settings.php, and that seems to have caused the problems. Now, the front page and nodes are being created perfectly.

adamgerthel’s picture

adamgerthel commented
Issue summary: View changes

improved text