Maintenance fixes only

Put your site in maintenance mode by uploading a file.

This module allows you to specify role specific fields. When creating a new field, you specify for what roles this field is enabled.

New Maintainer

We're happy to announce that @aaronbauman is joining the team of maintainers for this module. Thank you Aaron for donating your time and skills.

About Webform Registration

Webform registration was born from the need to allow visitors to fill out a sweepstakes form that would submit values to Eloqua and also create a new user.

At the time the webform register module did not provide enough flexibility to meet our needs, namely to allow a form to have many different field names (used for Eloqua mapping) and still keep track of which fields held the values for email, username and password to be used for user registration.

How is this module different from webform register:

• Maximum webform integration and flexibility
• You can add and fully customize every field that will be used for registration.
• If you are in a hurry, just add en email field and this module will handle the rest via a very user friendly and intuitive interface.
• Only the email field (webform component) is required, all the other components can be either generated by this module or omitted depending on your needs.
• Optionally you can specify all the labels and descriptions for all five fields (components): email, username, password, password confirmation and email confirmation

Take if for a spin and see for your self, this module won't let you down.

Similar Modules:

Features Override is used to change (override) existing Features. You may want to use it if:

• You are installing a feature module that requires this module.
• You have a site built on features - e.g., an Open Atrium or Commerce Kickstart site - and you want to make changes without losing them when you upgrade to a new version.
• You are a feature developer looking to selectively override components (Views, content types, etc.) of existing features and export just the changes to code.

Initial 1.x development sponsored by Chocolate Lily. The 7.x-1.x branch was unstable with several reported issues for views (and, likely, panels). That branch has been abandoned with new development occurring in the 7.x-2.x branch (sponsored by Phase2 Technology). Drupal 6 users should continue to use the 6.x-1.x version...no 2.x branch is planned.

NOTE: Overrides exported with version 1.x are NOT COMPATIBLE with overrides exported with version 2.x. If upgrading you should disable the 1.x override, remove the 1.x Features Overrides module, install/enable the Features Overrides 2.x version, then re-export your changes as new overrides.

Drupal 8

For similar functionality in Drupal 8, please see the Config Actions module.

Requirements

• Features 7.x-1.0-rc1 or later, to include the fix to #984472: Add hook_node_info_alter.
• CTools

Extra action for Drupal event system.
Sends messages to selected Jabber account.
Useful, when administrator want to get messages immediately.