Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
The aim of the JavaScript Aggregator module is to improve performance of your site with less server requests and bandwidth per page. In Drupal 5, all the JavaScript files will be aggregated into one file and optionally minified. JavaScript aggregation was brought into core with Drupal 6, so the Drupal 6 version of this module goes one step further to minify that file.
It basically does the following:
Takes the $scripts variable and removes .js files using a regular expression
Generates a unique filename for any set of .js files
Creates and caches one file containing all .js files in files/js
This module defines the "hierarchical_select" form element, which is a greatly enhanced way for letting the user select items in a hierarchy.
Hierarchical Select has the ability to save the entire lineage of a selection or only the "deepest" selection. You can configure it to force the user to make a selection as deep as possible in the tree, or allow the user to select an item anywhere in the tree. Levels can be labeled, you can configure limit the number of items that can be selected, configure a title for the dropbox, choose a site-wide animation delay, and so on. You can even create new items and levels through Hierarchical Select!
For a good overview of what Hierarchical Select can do, look at this demo!
This module allows Drupal cache bins to be stored in files.
Comparison with other caching modules
memcache is the closest caching module. File Cache can be configured to use a memory based filesystem (e.g. /dev/shm in Debian) which is very close to what memcache does. File Cache can use network filesystems and this
is another use case where memcache is traditionally used.
apc can be used for cache bins too. If it's used for that purpose,
it's usually only for some of the critical cache bins like cache and cache_bootstrap.
boost generates caches of pages that are directly served by web
server. File Cache can plug in regular Drupal page caching and provide
very fast page caching but this still needs a bit of PHP to be
executed. Database access can be avoided altogether though. See $conf['filecache_fast_pagecache'] in README.txt.