This module exposes the 'upload picture' element to the registration form. It also gives you the ability to set a picture as required in the module settings.
The Role Contact module creates a "staff list" from the profiles of users in a particular role, e.g. "staff role". The user list is formatted via theme functions, with convenient header and footer fields. The sort order of users can be set via weights. A configurable subset of profile data is shown in the user list view, along with the user's picture along with a link to a per-user page, showing a (potentially different) subset of profile data. In addition, in both the list and per-user views, each user has a contact form - and is preallocated with a contact form category based on their name - that allows site visitors (both authenticated and anonymous) to send email to each user without revealing the user's email address.
The normal use case: a company or organisation wants to list a subset of its users as a "staff list". Some more senior staff members (e.g. CEO, president, directors, etc.) should be listed at the top, others alphabetically. Only some of each staff member's profile data should be shown - other data is only internally visible. It should be possible for site visitors to contact staff, but without revealing the staff member's email address directly to minimise snarfing of those addresses by spambots.
Note: this module has only been tested with MySQL.
Module that imports data from vBulletin into Drupal, including social groups, private messages, blogs and birthdays, even Photopost! Also a Drupal module that lets existing vB users login to Drupal.
This module was developed for The Webmaster Forums (yes, we do like Drupal's forum!)
Single Login is a session management system for Drupal. It allows the site administrator to create a policy to detect, and prevent, duplicate logins on the same account. This is obviously handy for a site that requires paid subscriptions. Once a duplicate login is detected from a different system, the first login gets logged out. The admin can set a policy that determines how often and within what time period a session can "ping pong" between machines. Should the policy conditions be met, the admin can specify an action,typically to block the offending account.
