No further development

Helps build line combinations.

Very Simple module. If you use CloudFlare.com in order to set caching for your website. This allows you to put your site into development mode and clear the cache on cloudflare with a few buttons. Once installed add the cloudflare options into the settings area under the System menu, and you should be set to go.

Block Search engine from indexing site and also unauthorized access while in development or in any condition you want to keep sites secure from others.

If you don't want to put your site in maintanance mode but want to prevent early access to your website during its development, then this module is very helpful for you.

You don't need this module unless you're either a developer or another module you're using depends on it.

Currently Drupal core does not offer any hook to do actions after a node/entity is insered/updated/deleted in Database.
So this module introduces several new Drupal hooks to overcome this limitation
- hook_entity_postsave
- hook_entity_postinsert
- hook_entity_postupdate
- hook_entity_postdelete
- hook_node_postsave
- hook_node_postinsert
- hook_node_postupdate
- hook_node_postdelete

Provide a variable: $prev_next_content for 'node.tpl' to display links of the previous and next node which are the same type with current node.

Similar project: Previous/Next API

Contrast with module: prev_next, this module is more simple, and most sites can use directly, e.g. http://www.w3cplus.com is using this module's function now.

This module demonstrates the problem identified in issue #999338: theme_image() alt attribute cannot be passed in $variables['attributes']

It should be made into test...

This is a simple module that lets the user chose a role at the registration form.
You can set the role you want to let them chose at admin/people/registration-role

This module shows an example how to maintain Drupal.ajax in Drupal 7. It is simple calculator with on-fly summarization

Provides soft-deletion/trash bin functionality for Drupal. Content (node/comments/taxonomies/etc) is "soft-deleted" instead of deleted outright, and can be retained for a configurable span of time before being permanently purged. All this is opaque to end-users as all soft-deleted content is pervasively hidden from them, but administrators can access and restore soft-deleted content when necessary.

This is a cheeky little module that attempts to insert some validation of URL parameters into Facet API, so that if someone pops something random into the URL it doesn't get sent to the search backend for it to choke there.

For example, it's possible to send strings to filter integer fields.

This probably isn't the best implementation of this stuff, but it works!