Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Movement of stable development release to main release candidate.
Removal of gzip functions causing white screen on some apache hosting services with google chrome depending on installed/ unavailable header/mime modules.
Compatible modules page added.
Options to use SymLinksIfOwnerMatch instead of FollowSymlinks as required by some web hosting.
This is the first release of Boost 6.x-1.x since 1.18 was released, more than two years ago. Since then, the dev version had evolved, but no formal release had been made. This version is identical to 6.x-1.19-beta1 (no issues had been reported). The 6.x-1.19 release was not good, since it was not tagged correctly.
This is the first release of Boost 6.x-1.x since 1.18 was released, more than two years ago. Since then, the dev version had evolved, but no formal release had been made.
First beta release of the Boost port to Drupal 7. Supports basic Boost functionality. There is no support for the crawler (which should be forked into a new module, using the httprl module) and the admin/stats blocks are not yet available.
Notes:
I've created some Lighttpd rules for boost, testing of them would be appreciated.
Exposed views filters are now properly cached.
This should be a very stable release, with no actively known bugs.
This should be an awesome release. Please report any bugs or WTF's you encounter.
Notes:
I was able to identify a bug with the FieldAPI so the beginning part of the buttons on the boost page have a number added to them as a way to get around the bug; or at least identify when Drupal is screwing up, and prevent the wrong operation from taking place.
The flush button will now say flush or expire based on your settings. If that page is already expired then it will always say flush.
You can now leave the url_alias option turned on in the crawler and it will be smart about what url's it crawls.
Multi site flushing works a lot better now.
301 redirects are now killed from the cache (404 & 403 where already taken care of).
Overwriting of the cache is no longer required for "Do not flush expired content on cron run, instead recrawl and overwrite it" to work. This BTW is a huge win for performance.
Notes:
If you have encountered the bug in which a logged in user that just logged out gets the logged in page after hitting the logout link, then this 6.x backport core patch for the htaccess file should fix the issue. http://drupal.org/node/550488#comment-1931780
A new check has been added to check that the boost_stats.php file/menu callback is in your robots.txt file. I got a report of that page getting crawled. This should take care of that. Simply add Disallow: /boost_stats.php on a new line inside your robots.txt file.
Notes:
If you used hook_boost_preprocess() or set the pre-process function then the API has changed. Both have these variables passed to the function ($path, $data, $extension).
There are a lot of database updates in this release. If you previously set some custom expiration times for views, they might be lost in the update. The ones that can't be updated will be deleted; check output from boost_update_6117() for info (including the settings that got deleted). In short copy output from This setting needs to be re-set... as it will contain the deleted values.
One of the bug fixes has to do with the htaccess rules, suggest you update your rules.
Notes:
I recommend updating your htaccess rules from the admin/settings/performance/boost-rules page. They now change based on the settings, means you only get what you need, thus a slightly faster Boost.
See past notes for any tips on upgrading from a previous version: boost 6.x-1.0, boost 6.x-1.01.
Notes:
Because of new menu changes, you need to press the Clear cached data button located on the "admin/settings/performance" page.
If your using the latest version of Authcache, there is a slight chance Boost will not work with it. To get around this issue, disable this setting in Boost:
admin/settings/performance/boost
Boost advanced settings
Asynchronous Opperation: output HTML, close connection, then store static file. Run php in the background. When a cached page is generated, this will allow for faster page generation; downside is the headers are not the standard ones outputted by drupal; sends "Connection: close" instead of "Connection: Keep-Alive".
You can grab the new rules on the performance page under Apache .htaccess settings generation. Right now it generates the rules for boosted1.txt; looking into making it do others. Detects subdir installs and generates the correct rules.
In order for the one of the bug fixes and the new features to work, you need to upgrade your old .htaccess file. The new rules can be copied from boosted1.txt or boosted2.txt depending on your setup.
#289674: Supporting cached pages for authenticated users: Got rid of the embedded user ID in the cache directory name. It only annoyed people, and as long as the module only supports anonymous users it is simply of no use. In the future, avoid premature feature creep.
Note: This is experimental software meant for advanced users; assume nothing works, and you may be pleasantly surprised. And when it breaks, throw the broken bits at the issue queue.
The very latest version for Drupal 5.x. Tends to be relatively stable, with new features only occasionally being merged or backported into CVS. Recommended for expert users who feel comfortable submitting bug reports for the occasional unexpected glitch.
The very latest version for Drupal 4.7.x. Tends to be relatively stable, since actual development happens elsewhere, with new features only occasionally being merged or backported into CVS. Recommended for expert users who feel comfortable submitting bug reports for the occasional unexpected glitch.