File Force Download can be used to force the user's web browser to download the file to disk instead of displaying it in the browser window.
A streamlined interface for building Views. Administrators make a few simple choices (What kind of content should be listed? Do I want to sort by date, or by title? etc.) and a view is generated on-the-fly. Because the Views API is used, the resulting views can be modified using the full Views UI module.
In addition, every content type gets a simple checkbox on its configuration screen: "Make a listing page for this content." When it's checked, the module... makes a custom listing page, complete with RSS feed, filtered to just that content type.
User restrictions blocks users from registering or logging in based on name or email masks making it useful for fighting spam accounts. E.g. If it is undesirable to have users registering with a hotmail email address, %@hotmail.com may be denied. This module is a drop-in replacement for the 'access rules' functionality which was removed from Drupal 7 [1].
The module implements an API and custom hooks that allow third-party modules to add additional restrictions, or implement new type of restrictions.
This module provides configurable blocks of menu links with advanced features not available in Drupal 8 core.
The RealName module allows the administrator to choose fields from the user profile that will be used to add a "real name" element (method) to a user object. Hook_user is used to automatically add this to any user object that is loaded. It will also optionally set all nodes and comments to show this name.
This module is a simple implementation of the XRDS-Simple spec, which used to live at: http://xrds-simple.net/core/1.0/.
XRDS-Simple provides a format and workflow for the discovery of resources metadata, and other linked resources.
XRDS-Simple is an important part of the DiSo project ( http://diso-project.org/) and used by OpenID and OAuth for service discovery.
The idea behind the module is to simply assist someone with keeping an I Ching journal, not to automatically calculate the hexagrams themselves. For example - you give the I Ching Journal module what the lines are and it's job is to look up the hexagram number(s) for you, nicely highlight any changing lines, and provide an archiveable/searchable record. You can even categorize your entries (well, at least if you enable taxonomy ;-).
If you don't know what the I Ching is and would like to learn more, the Wilhelm/Baynes book is a recommendable starting place.
The 7.x version of the Taxonomy Autotagger module implements the interfaces created by the Tag API module, allowing a vocabulary to be searched against for suggestions of terms related to the content of a node.
Due to work constraints, the 5.x version of this module is no longer supported, whilst the 6.x version is only minimally supported.
ThemeKey allows you to define simple or sophisticated theme-switching rules which allow automatic selection of a theme depending on current path, taxonomy terms, language, node-type, and many, many other properties. It can also be easily extended to support additional properties exposed by other modules. In combination with Drupal's theme inheritance you can easily achieve features like:
Flag is a flexible flagging system that is completely customizable by the administrator. Using this module, the site administrator can provide any number of flags for nodes, comments, users, and any other type of entity. Some possibilities include bookmarks, marking important, friends, or flag as offensive. With extensive views integration, you can create custom lists of popular content or keep tabs on important content.
Flags may be per-user, meaning that each user can mark an item individually, or global, meaning that the item is either marked or it is not marked, and any user who changes that changes it for everyone.
In this way, additional flags (similar to published and sticky) can be put on nodes, or other items, and dealt with by the system however the administration likes.
