No further development

This code supports the Em Space Installation Profile experience.

The wf_required_fields module allows you to configure which fields of a CCK node are required, based on the workflow state of the node.

Required fields are marked on the node edit form. Also, transitions are objected (with a suitable message) if required fields for the target state are missing.

The module was tested with the field types that come with the CCK module. It should also work with other CCK field types that use CCK for database storage.

This module does nothing on it's own, but is required by DBFM to display pop-up windows.

The netFORUM Views module relies on the netFORUM xWeb Interface and netFORUM Dynamic Facade Nodes modules to pull a list of objects from a netFORUM database and present them as a page or a block, much like the Views module. It uses the same syntax as the netFORUM Dynamic Facade Nodes module, which is the same as Correspondence Templates in the e-Marketing module of iWeb, including conditional statements.

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.

This modules provides actions (as defined by the Actions module) to help manage media files. Currently, it implements storing video files from CCK nodes on blip.tv (uploading, updating and deleting the file).

Drupal 6 Status: we are waiting for CCK and emfield to work properly in Drupal 6 before finishing the port of Media Actions to D6. In the meantime, we started porting Media Actions to Actions 2.0, which is a backport of Drupal 6 actions into Drupal 5. You may want to try that; it is not fully tested yet. Get it from CVS HEAD.

Retired - No Drupal 8 version will be released

cck_blocks has had a long and fruitful life, beginning in Drupal 5, back when fields on content types were a contrib module named CCK (Content Construction Kit).

Please use the more modern Field as Block module to replace your cck_blocks for Drupal 8.

This module integrates the standards-compliant XStandard WYSIWYG editor by Belus Technology, Inc into Drupal.
XStandard meets very high accessibility requirements. See this blog post at Standards Schmandards for a thorough comparison with other WYSIWYG editors. A feature chart is available at the XStandard website.

This module allows you to add a progress bar to any node creation or edit form. You can set the delay before the progress bar appears.

This can be usefull if for example your node contains video fields, or any other field that takes time to process.

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.