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.
This module enables you to easily configure DFP Small Business (formerly Google Ad Manager) Ad Slots for Drupal. Each defined Ad Slot becomes a block and can be added to a region. You may also use [google_ad:ad_slot] to display Google Ad Manager ads within your content.
With this module you will be able to create interactive videos, question sets, drag and drop questions, multichoice questions, boardgames, presentations, flashcards and more using Drupal.
All the content is HTML5, meaning it will work great on smartphones, tablets and other mobile devices. With H5P, you create and edit HTML5 content directly in your web browser just like you edit any other Drupal content.
Show ads from a OpenX (formerly OpenAds) server. OpenX is a open source online program that will allow you to catalog and display advertisers, just like Google, Yahoo or Microsoft. This module allows you to show some ads in your site.
This module provides a dynamic way to add new customer profile types for the Commerce module using a UI. So if you want another customer profile type other then the default billing pane that comes with Commerce, you can now easily add new ones using this module. Just as the billing profile type is fieldable and you control how fields are displayed, the same is true for any profile types you create using this module.
This module requires an active UPS.com account in order to obtain estimated shipping rates.
Once installed, the merchant's UPS account settings (and other UPS shipping settings) must be configured at admin/commerce/config/shipping/methods/ups/edit. Please refer to the README.txt file for additional information about how this module works and how to get it up-and-running.
This module was designed to provide functionality that serves the majority of simple use cases. Advanced functionality involving multiple package sizes and types, void fills, and other custom-ish stuff will be considered once the simplest case is complete.
Installation and Configuration
Full details are available in the README.txt - be sure to read it before posting a new issue.
Install and enable the module and all dependencies (be sure to use the latest version of everything). Add dimensions and weight fields (new field types via the Commerce Physical module) to all shippable product types. Populate dimensions and weight fields for all products.
You MUST be using the commerce_shipping 2.x branch.
CRM Core is a set of modules for managing contacts, activities and relationships within your Drupal website. It is designed to provide a basic framework for managing these items and interacting with other components of Drupal.
CRM Core allows you to manage contacts, activities and relationships in your Drupal website. It provides extensive support for these entities, and includes a number of tools to make them easier to support in your Drupal website.
User Sync allows contacts to be paired with user accounts.
Match provides support for deduplication.
Reports provides a central repository for reports.
CRM Core Settings allows administrators to control the UI for managing contacts.
In addition to these basic features, CRM Core integrates with a number of other components within Drupal, including views, VBO, ctools, rules, solr, services, field api and search api.
The UC Add to Cart Tweaks product feature allows you to alter ways the add to cart form behaves for any product in your Ubercart store. The current tweaks provided allow you to empty the shopping cart when the add to cart form is submitted and to alter the add to cart redirect URL. Extra integration with Ubercart's product classes interface allows you to set default Add to Cart Tweaks on every product created of any given product class.
The Ubercart Donation Products module allows the creation of donation products. These products by default are not shippable and allow an end user to specify an amount to donate before adding it to the cart. Once added to the cart the user can there also change the amount of the donation.
The Donate module, which is included, provides a page listing donation products either by group or individually. This supplied page also allows the user to set various amounts for differing donation products and add them to the cart all at once.
An Amazon Store for Drupal. This is an implementation of the Amazon Product Advertising API (formerly Amazon Associates Web Service, or AAWS) for Drupal. You can install this and right away you have an Amazon Associates Store. Get yourself an Associates ID and then all purchases made through your store will result in a commission going to you. Allows searching, provides product pages, and manages a shopping cart.
Seeking new maintainer(s)! Are you using Amazon Store? I currently don't have it deployed anywhere, so it's not getting any love from me. File an issue in the queue if you're interested in maintaining this module. But FIRST, review some issues and provide some patches!
Panels module. (The 1.x releases work with Panels 2, the 2.x releases work with Panels 3). If Panels is installed, there is a default amazon item detail page and multiple panel panes provided so you can customize it.
If thickbox is enabled then you get large-size images when you click on a product image.
This module extends both commerce and webform. It allows the site owner to create webforms with a new product field. The productfield allows the listing of one or more products which the site user would then select from. When the form is submitted the products are added to the users shopping cart. The webform results page shows the submitted forms and intiially marks products as unpaid. Later, when the user has paid for the products in their basket, the webform submission is updated and all products that made it to the checkout are then marked as having been paid for.
The main use cases is for creating complex product selection screens. Webform is very good at capturing choices and offering options. The products that get added to an order can then be based on the results of the submission. An example would be a single webform which would offer registration to an event. All user choices could be captured in the webform, and product choices add to the shopping basket. For example, the main delegate attendance product is marked as mandatory on the webform meaning it has to be added to the basket. The optional wifi product could then be added as a second product field to the webform but not made mandatory. Alongside this the webform submission could collect other data about the delegate such as meal choices, seminar preferences or special access requirements.
This module was originally created by fago as a quick solution for a problem, which solved it well while no other solution was available. At this point in time however, there are more robust solutions that are not only available but architecturally superior, actively supported, and under continued development.
We recommend those interested in subscription / membership sites to consider looking at commerce_license module as a solution. Out of the box it allows you to create "subscription" products that auto expire after a given time and can assign/remove roles from users. I would guess that this is the 90% use case of people looking at this module.
There is a single issue of "extending" a subscription if an additional one is purchased which is being solved/worked on here: https://drupal.org/node/2193305
I will endeavour to work with other module maintainers and get a comparison of commerce_sp, commerce_license, commerce_recurring, and commerce_subscriptions. I will also be seeing about creating a migration class / helper module for existing commerce_sp users to migrate to commerce_license
This module is intended to make it fairly easy to manage opening hours for a large number of locations.
The use case this was built for is a chain of public libraries that have rather different hours, but common closing days. Originally, we used the office hours module, but the architecture and scope of that module did not fit well to this advanced use case, where we want to provide precise information on what libraries are open at a certain time.