Taken from What is Übercart?:

Übercart is a shopping cart designed for the Drupal CMS. Built on the rock solid framework of Drupal, it is designed to be a totally integrated cart system programmed in PHP/MySQL. The cart is not being developed in competition with the current e-commerce module but rather exists to address a different set of needs.

uBrowser is the new way to browse taxonomy for Drupal 5.x. It creates an easy to use interface for browsing vocabularies (categories) like you would browse a directory tree. Each term in the vocabulary is like a file folder, and clicking on it in the category select box will display all the nodes that have been classified with that term in the node select box. The look may be changed in the CSS, but other display options such as search forms, action buttons, and display names may be specified when the uBrowser is built for display.

Full documentation and various examples are available at:
http://www.ubercart.org/drupal_module_and_jquery_guides/ubrowser

E-Commerce add-on modules, tested with E-Commerce 3 beta 1; also appear to work with E-Commerce 2.1 (no guarantees).

These modules allow creation of product classes (aka types) and instances of those classes.

For us, it means the customer can pick which phone number he wants right at the product view page for "Toll-Free Number," for instance, and have that specific phone number reserved for him for up to X time while it is in his cart.

This project was sponsored by F2, Inc.

Key features:

• Items in cart are "on hold" (cannot be carted by anyone else)
• Each product class has a "max hold" setting to determine how long it can remain in-cart (and on-hold)
• Ability to stock several (selectable) instances of a certain product without adding clutter to products page
• Admin interface shows a table of which items are in-cart (and who has them in cart, and for how long)

Provides devnagari (India) transliteration ability to the edit elements of the nodes. using this module any drupal installation can start providing Hindi or Marathi typing facilities on the site.

The block configuration provides facilities to change the preference on which node the transliterator should work.

Google Summer of Code 2007

(Modified proposal and specification) – This will be revised in future.

A package of modules to restructure to implement the auto-completion through AJAX and refining the way filtering is done. The project, when all the options are selected, will enable the user to complete the links dynamically and along with the background architecture it will be done in a structured way, thus further extensions and configurations for personal preferences will be made effortless.

The package will contain three basic modules.

Ulink.module
It provides a protocol to interact with auto-completion. Tag [l|href|text|attributes] will be used to identify the insertion of links. Where href is the target referred, text is the text enclosed by the reference, and attributes along with the type of the link and its location guide the rendering of the link.

Basically it provides a skeleton for universal filtering. What is rendered and how it is rendered are completely determined in the configuration. Extensibility is guaranteed by implementing the hooks, specifically for nodes..
ulink_node() : to provide the implementations of node
ulink_node_settings() : to provide the settings form for node rendering
ulink_node_info() : to provide filtering tips to the user regarding the node rendering

upload_image.module takes uploaded images, that are attached to nodes, and creates image nodes from them. Thumbnails are shown in place of the file name in the list of attachements.

This module allows an admin to configure sub-directories of the site files directory to be used by the upload module. It requires the token module to specify the subdirectory pattern.

This module was developed by Palantir.net

This module adds an option to node edit forms to mark a page as 'protected'. When submitted, this generates a UUID and adds a path to 'protected/{UUID}' to the {url_alias} table. When accessing the node, only users with the 'Administer nodes' permission, the node author, and those with the correct URL can access the page.

I will release a stable version of this module once I've used it more extensively with my own site and hopefully after I've received some feedback.

A simple filter which adds a CSS-class to each URL according to its target. This lets you easily distinguish between internal and external URLs, and assign a unique style to each URL based on its destination.

e.g. <a href="http://blog.erdfisch.de">erdfisch :: blogs</a> becomes <a href="http://blog.erdfisch.de" class="erdfisch">erdfisch :: blogs</a>.

Sponsored by erdfisch :: internetlösungen - http://erdfisch.de/

Display URLs with corresponding favicon.

A simple filter which checks the content for <a>-elements and automatically fetches and stores the corresponding favicon.ico if available.
Generates and stores a CSS-file to stick the favicon to the URL at display time.

Sponsored by erdfisch :: internetlösungen - http://erdfisch.de/

URL profile collects URLs with a common host string and retrieves information for Alexa and Technorati about these hosts.

URL profile is to be used in combination with a feed aggregator. When the aggregator subscribes to a feed with articles from different sources (i. e. the Planet Drupal feed), URL profile finds out which sources those articles are coming from (in this case http://www.buytaert.net/, http://www.planet-soc.com/ ... ) and provides navigation by those sources. In addition to that, page thumbnails and blog rankings are pulled from Alexa and Technorati (API keys necessary).

Currently, the Leech module is the only aggregator that implements an interface to URL profile.

Check out http://leech.devseed.org/ for a demo.

The module was originally developed by Marcin Konicki and is currently maintained by Alex Barth. Aron Novak is the original author of url_profile_alexa.

The module is sponsored by Development Seed, the World Bank in coordination with Pierre Wielezynski and the World Resources Institute.

簡單的小模組，裝上之後在「輸入格式」中啟用，便可以自動把內文區域的網址、e-mail轉成連結。

一个简单的输入法过滤器，自动将http, ftp, email等输入转换成链接。

This is a simple filter module. It automatically converts URLs (http, ftp, email, ...) into hyperlinks.

Note: Urlfilter will be obsolete from Drupal 5.0.0 on, as this filter will be merged into core.

URLify is a simple module that generates the path alias of a node automatically using javascript. The alias is generated from the title of the node.

For more advance path management please see the pathauto module. You can stay up to date with URLify and Pathauto development by subscribing to the Paths discussion group.

讓使用者可以透過個人資料頁，自己新增 RSS feed 給網站。網站管理者可以：

• 設定可選用的、預設的分類，讓使用者選用。預設的分類可以不用顯示出來。
• 設定預設的更新間隔。
• 選擇是否要顯示在帳號設定頁。
• 讓使用者選擇一個或多個分類。

使用者可以選擇分類，所輸入的 RSS feed 會讓管理者進行檢視/核准。

User Aggregator allows users to add a syndication feed to a site's aggregator via their user profile.

Features:
Site administrator can set
- visible and default categories that will be assigned to user entered feeds. Default categories do not have to be visible
- default refresh interval for user entered feeds
- option to show on account setup
- allow users to select single or multiple categories
Users can select or unselect visible categories
User entered feeds go to a pending table for administrative review

Known issues:
Pure laziness made me use the MySQL-specific REPLACE command in the _user_aggregator_assign_feed() function, so this is not PostgreSQL compatible.

This module lets users delete comments on nodes they create without giving them full comment administration access. Permissions are on a per node type basis, so it's a great way to, e.g., allow users to administer comments on their own blogs.

Additionally, you can configure this module to force comments on selected node types to be approved before they get published. As with delete rights, this is administered by users so you don't have to do it yourself.

As with all new modules, please test before using on a production site.

Let users delete their account.

This module will be abandoned when http://drupal.org/node/8 is fixed.

Use this module to force all content submitted by a user to be associated with a term from a taxonomy.

Development sponsored by Vertikal.dk.

USE THE DEV VERSION - This module allows users to control just how much of their nodeprofile data is shared
with other users on a case-by-case basis.

Attempting to contact an 'unknown' user will allow them to choose to
a) send them a message, or
b) initiate a handshake.

The 'initiator' has the option to select which fields of his/her own to expose.

The 'acceptor' then has the option of
1) rejecting the handshake altogether;
2) accepting the handshake after
a) checking the fields of theirs they want to share(from the list the first user created),
b) selecting a handshake 'duration';
3) flagging the request for the admin and writing a note as to why the request may be inappropriate or a violation of the user agreement.

Whatever fields are deemed 'okay' by the 'acceptor' are exposed to both parties. (See the database table to see what information is tracked to make this possible.) A time limit may be placed on the transaction by either party. A handshake may be revoked at any time. It may be expanded and extended.

This module can also be considered a 'contacts' module as all users with whom a user has 'shaken hands' can be listed, sorted, etc. More robust contacts tools will be added as time allows. The goal is to eventually be able to add contacts like you would

IMPORTANT: Use the CVS Head version, rather than the 4.7 version. The 4.7 version is an old, buggy version, and I still have to figure out how to branch properly. (Using Eclipse in Linux if anyone can help out.)

This module creates several user lists, which may be viewed as pages and blocks. User lists may be displayed alphabetically, beginning with A-Z, by newest, by role, or as a list of users who have posted content of a certain type.

This module provides the ability for users to gain points when they do certain actions, such as posting a node, posting a comment, voting on a node, inviting a user, ...etc., and hence it is a powerful community building tool.

New: version 2.0 released. See details below.

This module aims to integrate all profile nodes in a neat and usable way allowing user permissions on all types associated with the user.

How?

If you use the Node Profile module, which allows you to tag any node types (usually CCK's) as profile nodes. You can also use Usernode and Node Family, however I never really found a neat way that tied the profile node's togther.

After chatting to dfletcher on IRC about this, he showed me some code he was using for a site he was working on. I based this module on that code and extended it further.

This module will take into account access rights to the node types - for example, you can create 2 CCK node types and tag them as profiles. You could then make 1 of them accessible by the authenticated user so they could provide details which you'd like them to maintain - like a normal profile. You could then setup the other node to be "private" so only a set of admins could use it. Useful for keeping notes on users or mayeb storing information about how they came to your site - eg if they were created during part of a marketting campaign? The combination of CCK, Node Profile and this module opens up the data you can associate with a user

This module allows you to create and enforce quotas on node creation and comment creation on a per role basis.

This is useful for the following scenarios:

1) Preventing random spammers or other miscreants from filling up your site with garbage.

2) Dealing with those over-enthusiastic users who join your site and then proceed to comment on every single forum post that's made. (Sure, you could just delete their posts, but that can make them angry. This approach is less likely to do that, and it will stop the damage before it starts)

In the future, I have plans to expand this module so that other modules (such as webform, upload, etc.) can use this module to store quota information and check resource usage against quotas so they do not have to implement that functionality themselves.

The module allows an administrator to disallow modification of user account/profile fields. The administrator can select which fields will be disallowed, or which fields will be allowed.

This module provides users with the ability to refer other users to a site they are registered at. When the new users registers, the referral is recorded.

Notifies administrator of new user registrations.

Allows users to create named relationships between each other.

This is meant as a replacement to the buddylist module. I couldn't wait for buddylist 2 so I rolled my own.

Admins create relationship types (friend, coworker, etc). Relationship types can be setup to be one-way or mutual. If a relationship type is one-way (subscriber) only the requester is shown as relating to the requestee. Relationship types can also be set as needing or not needing approval.

Admins can give users the option to auto approve relationships on a per-relationship type basis.

Also bundled with the core relationships module is a set of four other modules directly related:

1. User Relationship Mailer will (conditionally) send email notifications regarding relationship creation/removal/approval/disapproval/cancellation.
2. User Relationship Invites requires the Invite module and allows users to specify a relationship to a user that they invite to join the site.
3. User Relationship Defaults creates default relationships to any user joining the site (think Top on MySpace).

This module enables sites to automatically send customized email notifications on the following events:

• account activated
• account blocked
• account deleted

The first case is especially useful for sites that are configured to require administrator approval for new account requests.

UPDATE: This functionality is now part of Drupal core in version 6.x. I'm happy to report that http://drupal.org/node/144859 has been committed. Therefore, there will be no port of this module to the D6 API, since it's now part of D6 core. On the off chance that there are still bugs in the existing 5.x and 4.7.x versions of this module, those will be fixed and committed. Otherwise, all development on this module is hereby over.

Allows users to rate other users. Each user's rating (the voting results) is displayed on his or her user page.

Currently, there is no explicit voting functionality. A vote can only be cast by calling the API function uservote_set_user_rating(). The API is as follows:

uservote_set_user_rating($user, $vote)

Rate a user.

uservote_get_user_results($user)

Gets a user's voting results from the cache/database.

Notes:

• User Vote depends on the Voting API.
• The "Ratings" section on user pages can only be seen with the proper permissions.

The module adds information about user's content to his/her profile's 'view' tab grouped by content type. This allows to understand fast what is user's contribution for the site, that helps to add more community outlook to the site.

The difference from tracker.module is that it doesn't take additional tab and doesn't require additional click. Treats comments as seperate content type, what supposed to be an advantage; allows to locate each comment in thread.

Curretnly has lightweight implementation: doesn't require additional modules such as views and adds only one query per profile page view no matter how much content types it outputs.

It is a development version though, so any feedback and suggestions are welcome in this thread or via bug tracker.

This very simple module allows visitors to check username originality quickly using AJAX request during registration (completing registration form). This makes registration process more convenient as you don't need to submit your registration form to find out whether this username is already taken or not.

username_check module provides a button "Check availability" and a DIV with a warning message on the registration / create user form. It is assumed you will theme this form to make it look good.

Developed by ARDAS group - Web site development, Drupal services, Software development, IT outsourcing.

This module tries to make users nodes. It cares for automatic creation and deletion of a node for each user, the so called usernode.

This module (tested in drupal 4.7), first and foremost, creates a way to limit the number of nodes of a certain type that each user may create.

I am deprecating this project, in light of the fact that I have not been good at maintaining it, and that the nodefamily module and its related modules appear to do a better job of what I was originally setting out to do. I recommend looking into the nodefamily module.

強化使用者管理功能，包括：

• 用一個表單同時增加多個使用者。
• 為多個使用者指定角色。
• 同時刪除多個使用者。
• 移動多個使用者到不同的角色。

This module enables users to post a review of any node. This module is inspired by some of the user review functionality seen in the internet, such as amazon.com.

The utility module is a module that contains a bunch of utilities that are simple to code, everyone wants, but nobody actually codes them.
Right now, we have the following utilities:

System module fieldset closer

This utility closes all the fieldsets at admin/build/modules

Please add feature requests for anything you want
If you would like to help maintain this module, by all means, I'll let you! Just post an issue as a task

Maintainers: dmitrig01, sun, davea (TexasNomad), greggles, litwol