Under active development

Linkit Picker is an extention to Linkit.
Linkit Picker adds the possibility to "browse" links via views.

Current support for nodes, users and terms

This modules is using views to build tables with link data so its easy to customize if you would like to.

This module works as payment gateway for Ubercart of Tatra Banka, a. s. from Slovak republic.

Installation:
No special instructions to install. Upload and enable module as normal.

The functionality in this module was migrated out of the core MERCI module to make maintaining a more stable core possible. The develop of module will likely remain active after the initial pricing configurations are migrated.

MERCI currently supports 2 pricing modules:
Member Pricing - X free hours with X% discount
Daypart/Weekend Pricing - Days are broken up into morning/afternoon/evening prices

Selector lets you select a Features component to be exported to a feature right in the place in Drupal UI where a settings element for it resides. It provides a widget in that place near the element itself, which is giving you also information about the particular component and its presence (status) in available features.

At the moment it provides support for all core modules and these modules in addition:

Summary

The Values module is an interface for managing reusable sets of key-value pairs. The purpose is to allow lists of values to be reused across the website, without having the configure them in multiple locations, or in code.

Usage

To use this module, go into the Values administration page, at admin/structure/values, and you will see a table with the currently configured value sets.

To add a new value set, click on "Create a new value set" and fill out the information. You will be able to define the key-value pair for each option.

Overview

Comment Access allows your users to control the comments on their posts. It adds permissions to administer, approve, and delete comments on nodes they create without granting full comment administration access. Permissions are granted by node type, so it's a great way to allow your users to manage comments on their own blogs,

Aggregates a user's profile nodes into one.

You have several different pieces of profile information about your users regarding to their work, eating habits, leisure time, and so on, all of which are considered to be semi-private (ie. may be hidden from eg. unauthenticated users). You may want to make (some part of) their profile data merged into one node per user, possibly with some considerably different layout and/or access control. You have set up different content types: 'work', 'eating', 'leisure', and 'public_profile', all of them set up with Content Profile module--but how to merge the first three into the fourth?

Here comes profile_aggregator.module handy. Just select the source profiles ('work', 'eating' and 'leisure'), select the target profile ('public_profile') with the appropriate format, and let the users update their pieces of profile information while having Drupal do the merge part of the work!

Allows adding to/editing terms of/removing terms from vocabularies per role.

You have set up some vocabularies (with some terms) like Color (Red, Green, Blue) and Shape (Toroid, Cube, Sphere). Maybe you even have a vocabulary that controls who can view a specific node (with terms) like Access control (Editors, Colleagues, World). Here comes trouble: your precious editors want to add more Colors, or reorder the terms of the Shape vocabulary (probably they want to see Sphere before Cube, who knows,) and you do NOT want to grant your editors the administer taxonomy permission, as it grants too much power (and that implies too much sharing of responsibility). Without this permission they were NOT able to do the mentioned tricks: adding terms to a vocabulary but not to another, reordering/editing terms of a vocabulary but not another's, etc.

These problem of yours is the past--just download and install vppr.module, and set it up at Administration >> Site configuration >> Vocabulary permissions.

Allows textfield to be rendered like a node reference, with some autocompletion magic on edits.

A university department wants to list the authors on their publications' page. Any given publication may have several authors, both from the department and outsiders, with their order being important (ie. it is quite likely to have an 'employee-outsider-employee-outsider' like order.) If an author is an employee of the department, his/her name should be displayed as a link to his/her own profile page, while outsiders' name should be displayed as clear text. There are several use cases with high probability here:

1. It is quite likely to have an author order like 'employee-outsider-employee-outsider'.
2. It is quite likely that a now-outsider author becomes an employee later on, in which case his/her name should automatically converted to a link to his/her profile without any changes to the publication.
3. It is quite likely that the site editor wants to enter existing authors' names without typos, regardless of that they are employees or not.

So what does this module do then, anyway?

Let's switch to Drupal tongue. :) Want to have a nodereference-like link to a node that does not exist yet? Want to have autocompletion both on existing field values and on existing node titles of other content types? Install and enable this text_noderef.module, and all your problems fly away!

This module allows an administrator to define a date on which to expire a specific user account or to define a period at a role level where inactive accounts will be locked.

You need this module if: