Utility

Body Field Definition is a very simple utility features module. It provides a field base definition for a body field, which can then be used by one or more content types and allows the user to avoid any confusion over which content type should have the field base for the body field. This is particularly relevant for any site or group of sites being built with multiple features based content types to avoid any conflicts with each content type trying to declare it's own field base for the body field.

Translate your Website using the Services of https://www.euleo.com/

BundleClasses adds actual classes to Drupal. Out-of-the-box Drupal doesn't have very good Entity support. Entity API improves on that, but still Node and User etc aren't classes. And besides: all node types are completely different, so should have different classes.

Doesn't play well with:

1. stdClass Type hinting (don't do that):

The Simplenews module lacks a way to dynamically filter lists of subscribers for newsletters. This module hopes to remedy that by using Views as filters.

Simplenews filter allows you to select any view of type simplenews_subscriber on which to filter newsletter subscriptions against. The recipients must already be subscribed to the newsletter.

Changes some of the Drupal and Contrib default behaviours to be more reasonable.

EasyAd module is a targeted traffic module. It is integrating EasyAd.me mobile and online advertising tool with Drupal websites.

The project is under development.

For now, use EasyAd.me online advertising tool from EasyAd website.

The Entityqueue module is a great replacement for the old Nodequeue module, in that it creates a new entity type that takes full advantage of the D7 entity/field APIs. However, several commonly-used UI elements from Nodequeue have no equivalent in EntityQueue. Entityqueue Node Links adds "Add" and "Remove" links back to nodes that belong to node types that have entityqueues set up.

Provides a relative date token in the form:

[date:relative:time]

Examples:
[date:relative:-31 days]
[date:relative:-1 day:short]
[date:relative:-1 year:custom:Y]

Sponsors:
The New Group

This module does one thing, allow an admin user to define and interval of time that must pass before another request may be made by a particular user agent. This is most useful in cases where a search engine bot, for example, does not respect the request-rate set in the robots.txt file and it's repeated requests are impacting on site performance (requesting old pages outside of any caching layer for example).