Maintenance fixes only

This module generates a RewriteMap file which can be used to redirect requests for internal URLs to the corresponding alias. This allows the redirect to occur on the Apache level instead of requiring Drupal to bootstrap in order to handle the redirect thus removing significant load from the webserver to handle the redirects.

Usage

1. Install Drupal with Global Redirect module and this Global Redirect RewriteMap module.
2. Go to admin/config/system/globalredirect and configure settings for Global Redirect and near the bottom are the options for this Global Redirect RewriteMap module. Use the manual generation button to create an initial RewriteMap file.
3. The RewriteMap Apache directive cannot be used in the .htaccess context so the the following configurations must be placed in the server or virtual host configuration.
   

   RewriteEngine On    
   RewriteMap globalredirect txt:path/to/private/files/globalredirect_rewritemap.txt
   

4. Configure your .htaccess file to use the RewriteMap defined in step 3. Place these in your .htaccess just before the comment that says "# Pass all requests not referring directly to files in the filesystem..." You will also likely need to set the RewriteBase in your .htaccess. # Global Redirect RewriteMap
RewriteCond ${globalredirect:$1} > "" [NC]

Permalinks to Nodepath

This module provides a "File Compressor" field type that allows to archive and compress attached files to an entity into a single file.

Scald: SoundCloud is an audio provider allowing Scald module users to add Medi

The Responsive Preview module provides content and theme administrators with a quick way to preview how their site's pages will appear at narrow and wide width dimensions.

What is this module all about?

The Bundle Terms module enables administrators to tag entity bundles with taxonomy terms. The idea may seem crazy, but before you take out your pitchforks, look at a use case!

You've created a bunch of node types:

• Fire Trucks
• Fire Stations
• Firemen
• Police Cars
• Police Stations
• Policemen

You'd like to have a view that shows all of the node types related to 'Police', and another view showing all of the node types with related to 'Fire'. Using Bundle Terms, you can create those views without tagging any nodes.

Why would I use this module? Doesn't taxonomy already do something like this?

Yes, the core taxonomy module can replicate this behavior of these views, but it would require much more data being saved to your database. For large sites with many nodes, using core taxonomy functionality may not be a viable option.

The real difference is this: The core taxonomy module requires you to create a data point once per entity. Bundle Terms allows you to create a data point once per entity bundle. That's many fewer data points in your database.