Actively maintained

This module essentially combines ubercart products with the signup module.

This SAML plugin eliminates passwords and allows you to authenticate Drupal users against your existing Active Directory or LDAP server as well increase security using YubiKeys or VeriSign VIP Acce

This module integrate ALCAR Adhoc-EDI Version 2.7 API with Drupal 6 and Ubercart 2.

Content menu module improves Drupal's default menu management interface for tighter intergation of content authoring and menu management, so content can be created and edit right from the menu interface (e.g. creating content for a menu item that has been just created - watch screencast below).

About content menu module:

The goal is to make building a site's structure and content in one fluid process seamless, easy and natural. Editors can create content along with a menu item without ever really leaving the menu management process. Editors can find, associate and edit content right from the menu management interface.

Content Menu module makes building a structure-oriented website "page by page" with Drupal effortless and intuitive.

To get an impression of how easy content centric menu management is with the content menu module, watch our screencast: http://youtu.be/sYoYtoQ1s8c

HOW IT WORKS

Basically, Content Menu evolves Drupal's simplistic and isolated menu management interface into an editor's intuitive central for site authoring.

The most important new possibilties are to directly asses and edit a menu item's linked content and to directly create and position a new menu item with selectable target (content) type.

You can create a new menu item as …

• URL – With the traditional menu item form

Background

This module provides an "Argument-based" cache plugin for Views. It should only be used with Views that take arguments.

Traditional cache plugins generate cache keys based on everything available during the Views build process. This makes it impossible to flush a cache for a View only for specific arguments.

Take this example..

We have two node types: School and Class. A class node has a node-reference field back to a school. When viewing a school node, we use a view to show all classes that are linked to that school. Before this module, the best cache plugin would be Views content cache, which allows us to clear the cache only when a certain node-type is added/updated. We would set the cache to flush whenever a class node was created. But, why empty every single school cache just because one class was created?

With this module, you can target the Views cache for a given view, display, and provided arguments. There is also an option in the plugin to specify the amount of arguments to use to generate the cache key. This is useful if a view takes multiple arguments, but you only want to clear the cache for say, the first one. For example, the view takes a nid and date argument. The view will be cached for each date you're viewing, but when some action takes place, you'll want to clear everything just for that given nid.

Never let lack of a use case hold you back!