Actively maintained

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 project will try to integrate all scrolling and sliding libraries out there, into one modular framework. Famous example of similar approach is WYSIWYG which integrated most of the Rich Text Editors.

Resources

• Libraries API
• Comparison of Rotator / Slider modules

This module allows the admin account (user 1) to add fields, filters and sorts to views which use PHP code. It also supports additional accounts when the core PHP Filter module is enabled.

This module extends Drupal Commerce with a checkout pane that allows users to log into their account, register a new account or (optionally) continue checkout without an account.

The original (1.x) version had a different approach:

This module integrates Node.js with Drupal.

It provides an API that other modules can use to add realtime capabilities to Drupal, such as push notifications or chat. The module relies on a Node.js server application that maintains an open connection with the visitor's browser to enable instant communication. In order to use this module, you will need to install the Node.js application on a server.

This module provides one or more filters to views for filtering out nodes that have or do not have other nodes that refers to them through a node reference field. This can be useful when you need to list nodes that do have nodes that refers to it or vice versa.

The module let's you select which node reference fields you want to filter on.

This module works for both Views 3 and Views 2.

A CCK content field which lets you add a country to your content types; displaying country name, ISO 3166-1 alpha-2 code, ISO 3166-1 alpha-3 code or a countryicon with module Country Icons (6.x-1.0-beta2 and newer releases now supports Country Icons 1.x and 2.x).

Requires the optionwidgets module (CCK) and Country codes API.

Helper module to place and manage a humans.txt file in your site.

What is humans.txt?

It's an initiative for knowing the people behind a website.
It's a TXT file that contains information about the different people who have contributed to building the website.

Why should I?

You don't have to if you don't want. The only aim of this initiative is to know who the authors of the sites we visit are.