Under active development

Since Drupal 7 is more restrictive in allowing multiple failed logins, using different names (in 6.x version) is not needed any longer. These are the features of 7.x version.

• User one account is protected from viewing and editing. Users -- even with 'Administer users' permission -- will be denied access.
• User one account is hidden from user listing page, admin/people.
• User one account is hidden from user lists such as in blocks, Who's New and Who's Online. User One provides its own version of Who's Online block for correct count of logged in users besides hiding user one.
• User One exposes Drupal's built-in values to change otherwise inaccessible such as number of allowed login attempts and time window to remember such login attempts.
• While Drupal temporarily deny login after multiple failed logins, User One goes one step further to allow permanently block such IPs automatically and notify the site admin.

Generic (framework) implementation of Campaign Monitor Advanced module.

You can now extend this module to work with other services too. Plugins for Campaign Monitor and MailChimp are already provided.

Features:

• Support for multiple lists.
• Automatically fetches lists and fields.
• Asynchronous pushing of subscription and unsubscription requests. Reduces load and makes it more reliable and faster. Subscription statuses are locally available though.
• Map fields to Drupal tokens, profile fields and PHP code.
• Provides block per list. Provides block to subscribe to all lists at once.
• Custom field values for authenticated users are automatically calculated an not asked again.

Supported services

• Campaign Monitor (provided with EMF module)
• MailChimp (provided with EMF module)
• Interspire E-mail Marketer (provided via EMF Interspire module)
• Addemar (provided via Addemar EMF plugin)

Important note for people who upgrade from 1.1 to 1.2

This module will not be upgraded to 7, for that, please use subuser instead.

Use a drag-and-drop interface to customize layouts of nodes, views, comments, user data, etc. By defining custom view modes, one piece of content can be displayed differently in different places.

Sequential presentation of any of your site nodes, utilizing user chosen effects based on ajax asynchronous calls.

Why?
Indeed there are plenty of slideshow modules out there. So why creating one more?
We had to provide a good answer for the following requirements:

• Show a series of content items as slides using transition effect.
• Allow the user to navigate across slides using tabs and/or navigational buttons.
• Allow the content manager (non admin role) to fully control the contents & layout of each slide using node-based or views-based mode.
• Allow the content manager to easily publish / unpublish the slides and set their order of appearance.
• Allow the content manager to set the slides intervals, transition intervals and other slideshow relevant settings.
• Ensure the performance is content-agnostic i.e. allow the slideshow content to grow (number of slides and their weight) without impacting the slideshow page load time.

We could not find a module which fully suffice the above requirements (see comparison). Hence Ajax Slideshow was born.

Allows CCK forms to be filled without required fields before publishing.