Feeds Image Grabber (FIG) is successor of FeedAPI ImageGrabber, an addon for Feeds module, which grabs image for each feed-item from their respective webpages and maps it to an image field in the node created by Feeds (Node Processor).
This module extends the form API to include convenient access to common for submission filters and validation checks. The core form API has no built in validators available to you, nor filters, and all have to be manually placed in a validation function. With this module you simply add the basic filers and/or validators you want to have in your form render area.
You can use the existent filters and rules or create your own. This module is fully extensible using hooks, allowing you to easily add your own and reuse them throughout the site. Abstraction at it's finest!
This module allows users to have a public name, shown as attribution and identity but not used for login. There are some significant requirements you must know about if you choose to use this module. See also http://drupal.org/project/realname for a module that accomplishes a similar purpose, but is more sophisticated and complex in its approach.
The Global Avatar module is useful in multi-site environments where the user table is shared and avatars should be consistent across the network of sites. Specifically, it is designed to solve the issue raised in the post Multisite with shared user table, but how to share user pictures? This module is compatible with the ImageCache Profiles project.
Custom Node Template allows one to specify different node templates to be used on a node by node basis.
While there are many options for customizing the display of pages, fewer options exist for customizing the display of nodes. There are many instances in which customizing the display of specific nodes might be useful, and this module provides a simple and efficient way to achieve this.
If you are looking for a way to customize the display of all nodes within a content type this module would probably not be useful. While you can specify a node template to be used by default for a content type using this module, it only applies to nodes you create in the future. There are better solutions for customizing the display of content types - probably the best way is to just do this through your theme. You may also find some other helper modules to be useful. One of the main reasons for using this module would be to customize or override the display of specific nodes differently from the default display of those nodes.
Please see the Custom Node Template Handbook page for additional information and use cases to help you decide if you should use this module.
For users with appropriate permissions, a list of all node templates available in a theme are presented when creating or editing a node. Any node template can be selected to be used to display a particular node. Specific node templates can also be assigned to content types as a default. If a node template is not selected for a content type and specific node, then appropriate node template will be used by a theme as it normally would (per existing node template suggestions).
Adds a button field type for use with any fieldable entity type and Rules. Provides two different widgets: HTML Button and Image Button. Adds a new button click event, clicked button comparison, and reload page action for use with rules. When the button is clicked, an AJAX call is used to run the event. Using rules you could display a message to the user, alter some data on the entity (or another entity) and reload the current (or any other) page.
This module extends OpenLayers CCK input widget allowing to mark a location on the map by simply providing its address.
The integration with Token module allows to auto-fill other text CCK fields on the node submission page with values coming from the geocoding response (like city, country, postal code, administrative areas, etc...). Text and select widgets are supported.
Disables the user interface for creating and assigning roles and permissions so all permissions management can be done with code.
This adds an extra layer of security, as the site's permission can no longer be misconfigured accidentally.
This module was inspired the security paradigm of the Plone platform. See, in particular, 'Problem A2: Broken Access Control' in the Plone documentation.
This module allows administrators to moderate entity access by issuing licenses to site users. These licenses may optionally be set to expire at a predefined date and time.
This module provide a new "license" entity which can be used to moderate access to any other entity type(s) and bundle(s). These may be created via a (provided) user interface or programatically.
The license entity has the following base fields:
