Minimally maintained

This module integrates the open source applet Postlet into a multiple image upload page (which is linked to from the node/add/image page). This enables images to be "drag 'n' dropped" into Drupal.

The module requires the Image module to be installed.

The module is easy to install, and requires no user configuration.

Users of version 1 of this module may be disappointed in the changes that have been made, especially the removal of the bulk editing tool. This was a deliberate step to make the module as simple as possible, I'll be releasing a bulk editing tool for images (and any other node type) soon.

For more information about the Postlet applet, please visit the Postlet Sourceforge page. Bugs regarding the modules functionality should be posted to the Drupal site, whilst bugs regarding Postlet's functionality should be posted to the Postlet forums.

Development of this module was carried out by Simon Rycroft and funded in part by the EDIT project

Contrary to what is stated in the recent security advisory, there is no need to disable this module, unless of course you consider the following to be an issue:

1. Install imagex, image modules
2. Install http://drupal.org/project/content_access module
3. Create a user called "auth" that has no special roles
4. Grant "auth" the ability to create images
5. Go to admin/content/node-type/image/access and set "Enable per content node access control settings"
6. Log in as auth and upload some photos
7. Log in as an admin and visit the "access" tab on the recently upload images from "auth" user - should be /node/1/access if this is a fresh site
8. Take away both of the checkboxes under "View any content" and "View own content" and Submit the permissions
9. As the "auth" user visit node/1 - you should get an access denied
10. As the "auth" user upload a new photo
11. When the photo finishes uploading you see the thumbnails of the images that you have uploaded in the past hour, including the one that you should not have access to

If you're still concerned, please download the CVS version of the module, and install that.

This module uses JQuery and the AJAX File Upload Jquery plugin to present a preview of a user's new picture as soon as they select one. Uploads will be sent through the same validation process and errors will be reported immediately after selection has been made.

The PAM Auth module is based vaguely on a skeleton of the IMAP Auth module (http://drupal.org/project/imap_auth).

OG Contact provides a contact module style contact form for Organic Groups, and optionally provides a "Contact" tab on the group's main page.

Features

• Administrators can enable/disable group contact forms on a per group basis, or enable/disable contact forms for all groups at once.
• The recipients of form submissions can be the administrators of that Organic Group and/or a list of user defined recipients.
• Group admins can optionally be allowed to edit the information on their group's contact form, including recipients, and reply message.
• Contact form access can be restricted to a group's members.
• Group members be made contact form recipients if they have the "receive og contact submissions" permission.
• Administrators may create custom "Additional Info" text per group. Optionally, group administrators who can edit form settings may be allowed to add and edit this text as well.

Version for Drupal 7.x

There is D7 version in the works. Follow the D7 issue for updates.

Currently there is no supported upgrade path from 6.x to 7.x.

The D7 code is not ready for use in production. So far this is only available for testing, and may likely break.

Upgrading from 5.x to 6.x

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.