Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
My first Drupal project is for Drupal Commerce. I want to integrate it with Shipwire's robust shipping/stock API that I've used in the past in Ubercart and on other platforms (Magento, Shopify). Would love to hear from anyone else trying to create this tool. Thanks.
This module provides a field type for storing authors.
The module creates a custom content type called 'author' and store each author information using that content type. Fields such as email, biography, organizations, and picture are automatically created and added to the 'author' content type.
It also creates a vocabulary to store author's organizations. Module exposes a permission to control the addition of new terms into an organization vocabulary.
Rules OG Mail Actions Module Provides Rules Actions to send E-mails to all Members of an Organic Group in Different Formats. Currently drupal mail only.
Normal module installation.
HOW TO USE:
- Add one of these Actions to your Rule
- When Tokens module is enabled you can use Tokens to customise your Message
( [node:site-url], [node:title], [node:author-name], [node:ogname], [node:nid], [node:ogalias], [node:og-id], [node:field_mybodyfield-formatted], etc )
This module will provide context conditions to test and see if the current node belongs to a chosen nodequeue. Condition will return true if the current page is a node and if the node belongs to the specified nodequeue. Condition will return false if the page is not a node or if the node does not belong to the specified queue.
This is a small module that provides simple checksum for web accessible files.
This module was initially developed as a deployment assistant tool, to check if files were moved correctly from one environment to another. I thought that someone else might need such tool, so I uploaded it here to Drupal.org.
In the Privacy Per User module there are two settings; private and public, which allow the user to set the visibility of their profile, nodes or other site features on a Drupal site. This module integrates the User Relationships module with Privacy Per User to allow the user to select user relationships as well as private and public in their profile. For example a user could chose to share their photographs or profile fields only with friends, similar to the way in which Facebook works.
This module is currently being used on a production site and intranet using Drupal Commons (which relies heavily on user relationships to provide follower functionality).
Select the user relationships you'd like to test for on the Privacy Per User settings page (admin/build/privacypu/settings).
So we use google's email/apps hosting for cloud email and docs and have multiple Drupal instances all of which need to have users managed. This module allows you to authenticate users via OpenID using their gmail/google apps login and let Google manage the user's passwords with a single login to the Google Mail client.
It does this by adding a simple "sign in with your google apps account" to the top of the standard Drupal login form.