Automation

This module's functionality has been merged into the Rules and Views Integration module.

Adds a button field type for use with any fieldable entity type integrated with Rules. When the button is clicked, a Rules event is triggered allowing you to do actions such as display a message to the user, alter some data on the entity (or another entity) or reload the current (or any other) page. The module provides two different widgets: HTML Button and Image Button. It adds a new button click event, clicked button comparison, and reload page action for use with rules.

Designed to be the successor of the core profile module, which is deprecated for Drupal 7. In contrast to the deprecated module this module provides a new, fieldable 'profile' entity - leverage the power of fields!

Requirements

• Entity API - Version 1.0 beta 9 or later!

Comparison to user account fields

As described in the documentation Drupal 7 allows adding fields to user account pages - what serves as simple way for building user profiles. The main differences between that and profile2 are:

• With profile2 user account settings and user profiles are conceptually different things, e.g. with the "Profile pages" module enabled users get two separate menu links "My account" and "My profile".
• Profile2 allows for creating multiple profile types, which may be assigned to roles via permissions (e.g. a general profile + a customer profile)
• Profile2 supports private profile fields, which are only shown to the user owning the profile and to administrators.

Relationship to content profile

Extends the Flag Module to allow users to enter a note when they flag a piece of content and eventually build a flag history.

A state machine for paranoia, with the halting state typically entailing the implementation of a scorched earth policy response (i.e., erasing the Drupal database). Think DEFCON for Drupal.

This module is meant primarily for "paranoid" Drupal use cases involving information warfare. Typical users might be political dissidents in repressive regimes, BitTorrent bootleggers, various kinds of activists, and so on and so forth.

Basically, if you have adversaries trying to hunt & shut your site down or limit your ability to disseminate information, you'll probably want to install Lockdown to help maintain tight information discipline as well as to guard the perimeter and perhaps give you some advance warning when it's getting to be time to move shop.

Complete is looking for a new maintainer. If you are interested, please leave me a message via the contact form or make a new issue in the issue queue.

Complete is a simple module to instruct your users to perform certain actions in your website. It keeps track of the completeness of these actions. Complete harvests the power of rules to configure the kind of actions a user has to perform, and integrates with views for displaying the actions.

Behavior

• Rules integration. The module provides the condition "Is incomplete" and the action "Set complete". These should be added to all your rules that need to you want to track by this module.
• Views integration. A default view called "Complete" is provided, containing two blocks with listings of incomplete and complete actions, and a page with all rules checked for completeness.

Related Modules

• This module is related to Content Complete, but generalizes the concept of "completed fields" in CCK to rules. There are plans to integrate both modules.

Dependencies

• Rules