This module provides information blocks, regarding replication status between MySQL masters and slaves.
The user can set a block with a MySQL replication scenario; at one side master connection info and at the other side slave connection info. Then on block render the visitors can see a simple report, with the status of the replication and other useful information.
1. sub urls of node and user will be rewritten when the parent url has an alias.
2. you can use regex to rewrite any url if you want
NOTICE: no need to enable this module, just include the core in your settings.php
Provides a universal preprocessor handler for all media on a Drupal site.
More descriptions, use cases, usefulness to come.
Currently intended to be a handler for Sassy
[NOTE: This module has been deprecated as of June 2013 in favor of Cache Expiration. If you're currently using Boost Expire, please follow these directions to switch from Boost Expire to Cache Expiration on your site!]
A cache expiration module to go with Boost for Drupal 7.
Currently, Boost for Drupal 7 doesn't do any active cache expiration (see #1069438: How to Flush Boost Cache in Drupal 7.x), and this means that when you update a node, post a comment, etc., Boost will continue serving stale content from its static HTML cache until the file is finally cleaned up on a cron run.
For many sites, especially smaller sites where content is updated infrequently and cron may be run hourly or even less frequently, this means stale content will be served for quite some time, unless someone visits the Performance page and clears all the site's caches manually.
This module alleviates that problem by simply flushing Boost's static HTML cache every time a node or comment is posted or updated. You can set the module to respect your site's Minimum cache lifetime so it doesn't flush the cache until the minimum lifetime has passed.
This module may become deprecated in favor of a more universal solution (like Boost integration with the Cache Expiration module).
jStats allows you to aggregate statistics about visitors on your site, without breaking the cache-ability of your pages.
At its core, jStats could be seen as a bridge between the core Statistics module, that stores its data in Drupal but is incompatible with aggressive and external caching, and Google Analytics, that only adds a small JS fragment to the page and thus makes them perfectly cachable, but can't easily be accessed by Drupal modules (in order for example to sort a listing of node by the number of node views): it's a lightweight way to keep your statistic data in your database, that still works when the page you want to have statistics on is stored in cache.
Proof-of-concept module providing HTTP caching for authenticated users.
By default any response - currently only pages rendered through drupal_render_page() - may be cached locally by the user agent, except if explicitly set not to (e.g. certain paths, or if the page contains dynamic content that changes every request). Along each cacheable response an ETag HTTP header is passed containing identifiers of all displayed data (entities, etc).
Home of xsendfile integration for nginx and apache.
Merged Apache functionality with: http://drupal.org/project/nginx_accel_redirect
Drupal's regular menu system administration doesn't scale very well. This is due to the fact that for all node edit pages, node type edit pages and vocabulary edit pages (when Taxonomy Menu is active), Drupal loads all menu items from all menus in the system. For large amount of menu items, this slows down the system to an unusably slow speed, or even causes timeouts.
This is a known problem in Drupal core. This comment is from the menu module:
The prupose of this module is to pre-generate styles via rules.
DO NOT USE THIS IN PRODUCTION. THIS IS AN EXPERIMENTAL MODULE.
Normally the image derivates get created on request. But what if you want to display informations on presets, without displaying them. Like a download link with an info on size, resolution...then the image must already exist.
Implements a cache class based on http://en.wikipedia.org/wiki/Berkeley_DB
Thanks @miro_dietiker for the idea
