Under active development

What and Why

Drupal has expensive 404 errors. On an 'average' site with an 'average' module load, you can be looking at 60-100MB of memory being consumed on your server to deliver a 404. Consider a page with a bad .gif link and a missing .css file. That page will generate 2 404s along with the actual load of the page. You are most likely looking at 180MB of memory to server that page rather than the 60MB it should take.

That's where Fast 404 comes in. This module combines a very common method of handling missing image/file 404 errors (discussed here and planned for Drupal 8) with a method created by dpardo (a co-maintainer of this project) to deliver super fast 404 error pages for both missing images and bad paths. Depending on which method of implementation you choose (aggressive or super aggressive) you can deliver 404 errors using less than 1MB of memory on your server.

Drupal 7 Core Updates

Drupal 7 core has updated to add a rudimentary version of what this module implements. It allows you to set an excluded set of paths, a list of extensions to Fast 404 on, as well as the plain HTML that is delivered.

Issue describing: http://drupal.org/node/76824
Patch added: http://drupal.org/files/issues/404_fast_paths_7x-76824-328.patch

This module allows auto creation of groups associated with a particular node.

Dependencies

This module depends on Organic Groups.

Examples :
1. A site with football teams -- every football team is a content type and the administrator wants that everytime a football team is created Fan Clubs be created automatically created.
2.A site with a lot of movies, celebrities, etc might need to have a community around all these content.

The module prevents you from the hassle of creating all these groups/communities/fan clubs for every content of yours.

The module classified content types into three categories:
1. Group content types (community, fan club)
2. Post content types (content types that can be posted in a group, e.g. image, video, story)
3. Remaining content types (active ones -- groups can be automatically created for these content types only)

The module allows the administrator to decide what group content types should be automatically created for active content types. Once a combination is selected, the module also allows the administrator to set default organic group settings like title, description, directory listing, membership type, private groups, and active on registration.

Once configured, every team a football team is created, the fan club will automatically be created.

Provides field formatters for node RSS view mode:

Project summary

Create usernames based on a persons real name and save those values as user fields.

Tommy Lee Jones → TLJones

The Realname registration module is a solution for forcing professional usernames that are based on a persons real name. The Username on the registration form is replaced with First name, Middle name (optional), and Last name fields created and provided by the site builder. The first name, middle name, and last name are preserved in the defined fields, where it is later tokenized for further use.

Module features

Configurations

• Use your pre-existing first, middle and last name fields
• A choice of username format
• Force the first letter of last name, middle name, and first name to be capitalized.
• Force the actual username to be lower case. (This has no effect on the first, middle, and last name field values)
• Use regex to validate real names

Integrations

• Profile2 integration (7.x-2.x)
• Content profile integration (6.x-2.x)

Tokens

Realname registration provides the following tokens;

• First name & first initial
• Middle name & middle initial

This module is a contributed module for the The eXtensible Catalog (XC) Drupal Toolkit module.

This Drupal 7 module provides an input filter which can be used in text formats to allow users to use simple “[tip] Here’s a tip!