This module allows drupal site users to maintain lists of other users, like a typical email client does. It is similar to buddy lists, except that:
Initial development sponsored by Surge Communcations.
Notice regarding maintainence: With a change in employment, I am no longer able to maintain this project. If you are interested in maintaining this project, please use my contact form or privmsg me (zostay) in Freenode IRC.
The module is more than meets the eye. It's a faily complex syncing module that also show's the Invision system "inline" as content when you're viewing the forum (as an iFrame). However, Drupal is "King". All authentication is handled by drupal. Invision looks to drupal for authentication, and all registration is handled through Drupal.
Enforces minimum width and height settings for submitted user pictures.
Registration role lets an administrator select a role to automatically assign to new users. The selected role will be assigned to new registrants.
Be sure this role does not have any privileges that should not be given out to just anyone who registers. Because we shouldn't give away any real abilities above an authenticated user by default, this module really has only a few known useful applications:
OG User Roles allows group administrators of organic groups to grant additional user roles to individual members of a certain group.
Any additional permissions only apply within the context of this group and not globally. This means that the additional user roles to grant are determined and assigned by the requested page; e.g. node/123 belongs to group XYZ for which the user was granted additional roles. If the user goes to another page that does not belong to the same group, the additional user roles are no longer assigned.
Additional user roles can only be granted, not revoked.
Site administrators may also configure a default user role for new group members or a default user role for new group admins.
USE THE NEW 1.6 RELEASE - it should be stable and contains bug fixes. Looking for co-maintainer. See message in issue queue.
This module adds the ability to have several different membership types, each collecting different data from the user for registration by using custom content types and the combination of nodeprofile and pageroute modules (both required). The accounttypes module is recommended but not required. See each required module for any dependencies that they might have.
What this module does is:
When a user attempts to register for your site, they will first be presented with a drop down selector of membership types which you as admin have previously defined. They will read instructions for proper membership type selection that you previously wrote. After selecting and submitting this form, they will be presented with the standard Drupal registration form. Depending on whether you require admin approval of new accounts and/or email verification, the user will then either - a) be immediately presented with pageroute consisting of nodeprofile pages which will collect further data from them, b) be logged out so they can verify their email, then when they return be presented with the pageroute for their membership type as in (a), or c) after the admin has unblocked their account and/or the user has verified their email, when they return they will be presented with the pageroute as in (a).
In all cases, if you require that certain pages of the pageroute be filled out before the user can use the site, they will be routed to the next unfilled page at each login, or each attempt to browse to another page until they do. In other words, they will be stuck until they complete registration, except that they can logout at any time.
See the USAGE example in the README for how to setup nodeprofile, pageroute, and your content types. [Note: this needs updating in one respect. When you create your pageroutes, you must now specify tabs, not buttons or you won't see the return link from the 'Personal data' section of the user profile back to the main profile area.
Optionally, if you use my Account Types module (http://drupal.org/project/accounttypes), you can assign/associate an account type with a membership type. The README explains the difference between these two concepts and how they can work together.
This module is also aware of OG and my Content Type Administration by Organic Group module (http://drupal.org/project/og_content_type_admin). See the README for how this module interacts with these others.
The README contains the following:
--CONTENTS--
REQUIREMENTS
SETUP/INSTALL
FEATURES
USAGE (Example)
UNINSTALL
CREDITS
See the documentation link below.
This module is complicated to setup and use because of its dependencies. You must read AND UNDERSTAND all documentation for the nodefamily, nodeprofile and pageroute modules before attempting to use this one. Oh, and understanding CCK is a must as well. This precludes use by casual users, whether newbie or not. I'm willing to help, but I won't hold your hand.
Contact me via my Drupal profile if you'd like to hire me to set this module up, modify it for your particular use, or other Drupal/PHP work.
IDCard is a simple module that creates PDFs from user's information for the purpose of creating a printable Identification card. The module allows an administrator to define a badge template that is then filled in with information from the user's account. Examples would include security badges, identification cards, Conference badges, etc.
A template defines the background image to be used, size of the card (height, width), print orientation and has a PHP code area to define what user's fields will be printed and where. If the profile module is enabled those fields will be available for inclusion on the card. This module was created for Manhattan Neighborhood Network to provide physical ID cards for the Community producers, and staff.
This is used for the Summer of Code (extend case tracker module), it will eventually be merged as case tracker, but this is a place holder for code submission and testing purposes.
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. This module is sensible to standard Drupal username validation as well as Access Rules validation.
