Actively maintained

This module provides a simple way to show a short-term urgent message on the website. Think of CNN Breaking News, when they show a short message the top of the site (or the 'Welcome!' style messages at StackExchange websites). This module works for both anonymous and authenticated users by using a cookie, and recording actions in the database. This solves the need to show messages independent of the users authenticated status.

With User Alerts, you can:

• Alert users about breaking news, or a special same-day sale for ecommerce
• Schedule publishing of alerts via Scheduler
• Override display with TPL and CSS

How to use this module:

1. Enable User Alerts
2. Set the appropriate permissions for selected roles
3. Set the User Alert block in the appropriate region of your theme.
4. Create a user alert node.

You can also set some global settings for alerts at admin/settings/user-alert.

Unpublished alert nodes are removed from the system automatically. This is to prevent an old alert being seen by a user (if the cookie was cleared or expired, for example) if a node was republished accidentally.

Running Case Tracker and Organic Groups on the same site raises some questions - but CTOG helps solving them by utilizing some rules to tie them together in a way which makes them easier to use.

Let's assume the following scenario. The site serves a central hub for several groups of people to provide an easy-to-use interface for storing information while working on projects and solving cases. The different groups are consisting of different people, and each group has it's own project to work on. The projects are separated from each other: no person of group A should be able to access any stuff of group B if s/he is not a member of that one as well. Additionally, no case can belong to more than one project at the same time.

This is where Case Tracker and Organic Groups are kicking in (referred to as CT and OG from now on). CT is quite a good choice to serve as an issue/case management system, but does not have anything to separate the different projects from each other. OG is the responsible for access control. So, let's use node type "Project" as a "project" node type speaking CT language and as "group nodes" speaking OG language; let's use another node type: "Case" as a "case" speaking CT and "standard group post" speaking OG.

What's wrong with that?

7.x-1.x

The new epub module for Drupal 7 provides displays for file entity and file fields and enables users to read epub/ibooks files inside their browsers like pdf module.

Use this module with apachesolr_file (recommend with file_entity 7.x-2.x), you can build your owned online library.

• "ePub default" display uses iframe to wrap xhtml files extracted from epub package
• "ePub cover image" display shows the cover image inside epub file (A cover image is not required according to the ePub standard)
• TODO: add js epub reader in the future and need help to make something like Readium work on server side

6.x-1.x

The ePub module allows site administrators to enable other users to download the ePub version of the book contents available on the website.

The Internet Archive module allows sites to automatically transfer media files (audio & video) as well as associated metadata to and from Archive.org. Once files have been transferred, they can be displayed using Archive.org's embedded player, and derivatives can be retrieved.

Notes on forthcoming D7 Port:

• There should be a development release ready for testing towards the end of September / October.
• We're hoping to make it much leaner in D7, leveraging fields/entities in core, Media (http://drupal.org/project/media), and the upcoming Derivative API SOC project (http://groups.drupal.org/node/145074, http://groups.drupal.org/node/155449)
• Please post to the issue queue if you would like to help out with the port

The D6 development release of this module provides:

• ability to trigger manual transmission of files stored in CCK filefields, emfields or textfields
• an automated file transfer queue, capable of harvesting files from any view containing a filefield, emfield or textfield (dependent on drupal_queue, includes configuration options for days/times to allow transfers, can be triggered by drush command or cron)

This module gives basic revisioning functionality to Webform submissions. It is designed to look and function similarly to Drupal core's revisioning system.

Features:

• View, Revert, and Delete revisions of Webform submissions.
• Leave log comments per-revision (except for the initial submission).
• Resend email to recipients upon revision - requires Webform 3.x or later.

This module can be very useful if you wish to track edits to a submission.

Advanced gallery uses CCK nodereference and imagefield fields to make nice comfortable to work gallery for the multuiser site.