Actively maintained

This module adds a new node option Premium content along with core publishing options (Published, Promoted to front page, Sticky at top of lists).

When a node is published as premium content, only users with proper privileges may view the full content of the node.

Non-premium users can still access premium nodes but only get the content rendered in teaser context, even when trying to view the full content. An additional message informs them that the content is available to premium users only.

This is a module that extends the module context by adding more conditions and reactions.

Provides the following sub modules:

The Page Syndication module works in conjunction with Panels and CTools to create content that other sites can embed with a single line of JavaScript. Content can take the form of just about anything that can be put on a Panels pages, including polls, quizzes, forms or a calendar.

Key features:

This module enables you to make the Menu Settings required on specific content types.

It forces content types to be included in the menu system before the content will be saved. It removes the 'Add menu item' checkbox and makes the title field mandatory.

This can be useful in a number of situations, e.g. when using [menupath-raw] in the pathauto settings, which expects a node to live in the menu system.

This module makes sure it does.

The purpose of this module is to give site administrators the ability to change the input format of nodes en-masse. In particular it helps to solve the issue of users not being able to edit content they have created because the administrator has inadvertently removed their permission to use the input filter or has changed the input filter to something the author does not have permission to use.

It can also help prevent the commonly asked question, "Where has my edit tab gone?"

"The cck model for voting with Drupal" (source)

This module provides flexible voting widgets for nodes and comments.

Administrators can add multiple widgets. By default, there are 8 widget types to choose from:

• Thumbs up
• Thumbs up / down
• Number up / down
• Fivestar
• Emotion (this makes me mad, angry...)
• Yes / no
• Slider
• Custom

By using "custom" you can customize the rating buttons and Voting API mode. Widget types can be extended by other modules. Other features include:

• Views integration
• Nodes get an extra tab with voting results per widget, which shows:
  • Total vote count
  • Average rating
  • Total points (for thumbs up / down)
  • Vote count per button
  • Chart of vote count per button, per day
• Multiple ratings on the same node (i.e. for "comfort", "location", "services" etc.)
• Voting can be closed at a configurable period after node creation
• Start- and enddates can be configured per node, per widget

DrupalChat allows visitors of your Drupal site to chat with each other privately or together in a public chatroom. This module enables sites to provide online support for their products/services, and thereby increases user engagement. Also, it is useful for social networking sites, forums, blogs, etc. It logs the user conversations so that they can be later viewed in message inbox. You can try it out live here.

Description

Module provides integration with russian links exchange systems Sape, TrustLink, LinkFeed

--
Данный модуль помогает быстро и без ошибок интегрировать друпал сайт с биржами ссылок.

Модуль поддерживает мультисайтинг и корректно работает с кешированием страниц.

Версия 1.1 поддерживает Sape, Trustlink, Linkfeed

Crumbs calculates breadcrumbs for your site.
It does so by finding the parent of the current page, then the parent of the parent, etc, until it arrives at the home page.

Crumbs comes with a bunch of built-in plugins, that can be individually enabled, disabled and prioritized, and some of which provide further configuration options.

Extended History aims to help module developers (or PHP-savvy web developers) by keeping an extended history of visits to nodes for each user.

While Drupal already provides some basic funcionality in the history table, there are a couple of drawbacks:

• History records are purged after 30 days;
• That 30-day limit is non-manageable, unless you disable cron runs altogether;
• It doesn't count how many times each user saw that node.

Original code from node.module: