Content

The ACL module, short for Access Control Lists, is an API for other modules to create lists of users and give them access to nodes. It has no UI of its own and will not do anything by itself; install this module only if some other module tells you to.

We're aware of the following modules using ACL (let us know if you know of others):

• Content Access (optionally uses ACL to provide by-user access control)
• Flexi Access
• Forum Access
• Image Gallery Access

Update: For Drupal 8 please use the redirect module. This project is deprecated for D8

What?

GlobalRedirect is a simple module which…

1. Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
2. Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.
3. Checks if the current URL is the same as the site_frontpage and redirects to the frontpage if there is a match.
4. Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method.
5. Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's.
6. Make sure the case of the URL being accessed is the same as the one set by the author/administrator. For example, if you set the alias "articles/cake-making" to node/123, then the user can access the alias with any combination of case.
7. Most of the above options are configurable in the settings page. In Drupal 5 you can access this after enabling the globalredirect_admin module. In Drupal 6, the settings page is bundled into the module.

The Monument module is designed to display and organise photographs or other images of historic monuments. Each image can be related to a specific part of a monument and the module can take care of displaying many image thumbnails at once to give an impression of the layout of the monument. The current version provides a 'compass rose' type arrangement for display at the moment.

For Drupal 6, this module is being replaced by the Dashboard project as part of the drupal.org redesign. We need volunteers to work on Dashboard, so go over there and help out, please.

The Drupal 5 version still works, but is not actively being developed. I have marked the module as 'Obsolete.'

MySite pages let users create a personalized summary of the site by adding selected content elements to their personal page. The MySite module is similar to tools like MyYahoo!, iGoogle and NetVibes. However, the content available is generated from your web site.

The module allows registered site users to create a MySite page that contains content from throughout the site. For sites that use the Aggregator module, users may also add feeds from external web sites to their MySite pages. MySite also supports Blocks, Views and 'Droplets' -- content widgets created by the site administrator. Users with JavaScript can drag, drop and sort content on their custom personal layout.

With Droplets, site administrators can also expose web-based content widgets like those from Google and WidgetBox to their users.

The 5.x.3 release adds multiple page support, so that users can have more than one personal page.

MySite was written using an API/Plug-In model that allows the core module to be extended to handle additional content types. These content types do not have to be nodes.

The Exif module allows you to display Exif metadata on image nodes. Exif is a specification for the image file format used by digital cameras.

Roadmap (order by priority) for drupal 7 & 8 versions:

• Work in Progress (current development in 1.x-dev versions):
  • automated test suite
  • Drush : tree folder import (import images in a folders and sub folders).
    This is working on 8.x branch. backport in branch 7.x in progress.
  • make vocabulary structure optional (flat vocabulary),
  • support automatic title based on image metadata. see #1606294: Automatic Node title from EXIF: generated title does not appear until drush exif-update & then deleted on subsequent node save
  • add a sub module exif_content with some media type and content type
• Followed by :
  • integrate with core/imagecache to rotate image from exif data if desired
  • exif_location adaptation to drupal 7 and 8
  • add support to Views Bulk Operations (VBO)
  • update metadata field of image in file (see #766322: Write and Edit EXIF/IPTC)
  • migration tool from php extension field names to exiftool field name

This Module integrates the famous 'Liga Manager Online' into Drupal.

Of course you need an actual version of the 'Liga Manager Online', so download it 'here'!

Features:

Viewfield provides a field that holds a reference to a View and renders it whenever the entity containing the field is displayed.

Features

• Author chooses one or more views and displays from a list.
• View arguments (contextual filters) may be supplied literally or through tokens.
• Administrators may restrict which views and displays may be assigned.
• Administrators may supply default values that will be used for all entities in a bundle, making it unnecessary to supply field values for each piece of content.

The publishing module is primarily a glue module to make it easier to handle article publication in a standard form.

It helps you define and create a workflow, provides a page to make it easy to see what state the articles are in, and provides tools to help ease things along.

In order to use this module, first I suggest you read this article: http://www.angrydonuts.com/publishing_articles_a_tutorial

The module currently in CVS is for 4.7

Node History is a replacement for the revision list built into the node module.

With this module you can configure which columns are displayed in the revision list and how they are formated. A hook is provided for other modules to add columns or format rows and columns.

The columns provided by this module are the same as the built-in ones (vid, author, date, operations, log message).

This module allows you go to the edit page by double clicking on any internal link to an item.

Users with the proper permissions can double-click on:

• node links to go to the node's edit page
• user links to go to the user's edit page
• comment links to go to the comment's edit page

This module also creates hook_dblclick() which allows other modules to provide double-click, shift-double-click, and alt-double-click behaviors. See the module code for documentation and examples.