Under active development

Provides streams of status updates like Twitter or Facebook's "wall" feature: each user/node/group/taxonomy term/whatever can have a "stream" or microblog where users can express their thoughts to the community. @mentions and #hashtags are supported, as well as comments on status updates, viewing conversations between users, the ability to "like"/"reply" to/RT a message, automatic updates without page refreshing, and integration with over 25 modules.

Facebook-style Statuses is moving to the Statuses namespace for Drupal 7+.

According with Wikipedia, a graph is a set of objects called points, nodes, or vertices connected by links called lines

Allows users in permitted roles to add custom help messages to any specific path or path pattern, for display to selected roles, along with help messages provided by other modules.

The File (Field) Paths module extends the default functionality of Drupal's core File module, Image module and many other File upload modules, by adding the ability to use entity based tokens in destination paths and file names.

In simple terms, File (Field) Paths allows you to automatically sort and rename your uploaded files using token based replacement patterns to maintain a nice clean filesystem.

Features:

• Configurable file paths now use entity tokens in addition to user tokens.
• Configurable file names.
• Support for file based fields, including but not limited to:
  • Drupal core File module
  • Drupal core Image module
  • Video module.
• File path and filename cleanup options:
  • Remove slashes from tokens.
  • Filter out words and punctuation by taking advantage of the Pathauto module.
  • Convert unicode characters into US-ASCII with the Transliteration module.
• [D7] Automatically updates unprocessed file paths in any Text fields on the entity.
• Retroactive updates - rename and/or move previously uploaded files.
• Active updating - actively rename and/or move previously uploaded files.
• Automatically create an redirect when moving uploaded files using the Redirect module.

This module will prevent users under the age of 13 from logging in if their respective parent or guardian (P/G) have not "signed" their COPPA compliance form. If a users Date of Birth -- stored in their user profile -- cannot be determined, the user will not be allowed to login.

P/G to child relationships will be loaded into an internal {coppa} table. This table will track the Parent to Child relationships and monitor when COPPA compliance was first achieved.

Suggested setup;

1. enable profile module
2. enable coppa module: this looks for a profile field called "Date of Birth" (profile_dob) and creates it if not present.
3. create a user role that will require COPPA compliance suggestions (student, etc.)
4. visit 'admin/settings/coppa' and select the above user role
5. also visit 'admin/user/coppa/add' to add parent/child relationships
6. also visit 'admin/user/coppa/manage' to manage existing parent/child relationships

Any users with the role you select at 'admin/settings/coppa' will now require coppa compliance to login and use the site. Please be careful in choosing the role; using "authenticated user" can lock all users out of the system if they do not have a profile_dob over 13 years from the current date.

Using this module, organizations of any size can integrate their Drupal website with LoopFuse OneView to automate marketing processes. LoopFuse is an open source solution that enables enterprises to automate web activity tracking, lead qualification and lead scoring activities. Acquia funded the development of the initial version of the module as part of their effort to connect their corporate Drupal web site with the LoopFuse OneView application. LoopFuse has taken over the project for version 6.x and, as such, the modules do differ in scope and dependency.

Requirements

• A LoopFuse account is required for this module to work. A FreeView version is available.
• CRM Software. Right now LoopFuse only works with Salesforce.com, so you need a Salesforce.com account (30 day free trial available)
• Version 6.x requires the Webform module for forms integration.

Credits

Current Maintainers:

• LoopFuse

Version 6.x Contributors:

• LoopFuse