Content

Fill a Webform field with the value of a node field.

User case example

Use an email address from a node as the destination for the webform to be sent to, based on what the visitor has selected on one of the webform fields.

More detailed example…

An example usage is that there is a Sector content type that includes an Email field, which provides the email address for the contact person of each sector.

Removes Webform submissions from the database once they have been emailed.

Useful if you want all the features of Webform, but don't want to store any of the information it collects in the database.

How often do you see old content dredged up and start to fly around social networks? Do you ever see people commenting or asking questions on posts you wrote several years ago?

It's quite usual to see dates on articles, but sometimes it helps to make an article's age a bit more obvious.

"Out of date" adds a message at the top of content, when the content is older than a set interval (which, by default, is set to 6 months).

Useful for creating letter writing campaigns aimed at newspapers and other publications using webforms. Provides a component for Drupal webforms populated with selectable publications. If configured, to collect a zip/postal code from a component on a a previous form page, the publications component will reduce this list of publications to those with addresses in a set range.

Sponsored by the folks at openmedia.ca and New/Mode.

Book Explorer provides an explorer-like book navigation block. Instead of clicking on a book page in order to see its child pages, you can simply click to expand (or collapse) each book page. This provides a much faster and enjoyable experience than having to wait for a browser refresh.

Book Explorer provides a block that replaces the 'Book navigation' block in core. It is identical except that the 'Book explorer navigation' block has expandable/collapsible tree items.

just a proof of concept that single_page_website module can be improved a little bit :)

This module extends the Field Group module by adding the ability to override the default title of a field group item (horizontal and vertical tabs, accordions, divs and fieldsets) on a per node basis. This means if you have a content type with 3 tabs, e.g. Movie Name, Lead Actor, Supporting Actor, you can create you can create field groups in the manage display, and override the titles like so:
Node 1

This module really sorts by creation date!

Unlike similar module like Sort Comments or Comment goodness this module sorts the comments by the creation date ('created' timestamp to be precise)

Not only in flat, but also in threaded display!

Usage

Configurable per content type in the comment settings fieldset.
You can also set the order

D7 version of http://drupal.org/sandbox/seanlwatkins/1510620

Original Issue: #1304196: How should we do weighted Relations?

Problem Overview

Relations need weights. There are three primary use cases I have found for this: