Planet Drupal

This screencast demonstrates how to do custom per-product email notifications. After adding a multivalued "notification" field to the product, we can check through the order on order completion to see if there are products which have product owners who need to be notified. The logic is "When the checkout process is completed", Loop through the line items in the order. For each line item, call a component (a Rules subroutine) that checks to see if the line item is associated with a product, and if so, if it has notification fields filled out. If so, the action is to loop through the emails in the multivalued notification field and send a tokenized email to each one.

Before getting started I mention the three things that persistently give people trouble with Commerce and Rules, and some solutions:

1. Not understanding rules in the first place: Spend a few hours starting from the beginning with Itangalo's outstanding "Learn the Rules Framework" video series.
2. Not understanding how to bring related fields and entities into scope: Read the FAQ about bringing fields into scope from the Drupal Commerce FAQ.
3. Not understanding how to use conditions in a loop or how to use Rules Components (subroutines), which is something we'll demonstrate here.

Here's the screencast:

There are many automated payment methods for Drupal Commerce around, we have solutions for Paypal, Authorize.net, Ogone and of course a lot of local banks, but there are some that are also widely used and are somehow "manual", we're going to take a look to three of them:

• Commerce Bank Transfer allows to input bank information that is going to be displayed to the user so they can note that down and make a wire transfer for the total of the purchase.
• Commerce Cheque and Commerce Cash on Delivery are quite similar, both of them need some information filled in their settings that is going to be exposed to the user so they can follow the payment instructions, however the intention of the modules is quite different as one is for cheque payments and the other to pay when the items purchased are sucessfully delivered.

The three of them need some manual action from the store administrator to actually confirm that the payment has been done.

Commerce Bulk Product Creation was the first contributed module to the commerce project and provides a quick way to create multiple combinations of products with a single form submission. It also optionally manages the creation of the display associated to the product variations in different ways such as generating a display for each product created in bulk.

Some conditions in the product configuration need to be met in order to use the bulk creation feature, you need to have one or more fields of list type, boolean or term references with the submodule for taxonomy support. There's also support for Entity Reference fields with the BPC entity reference module.

Note that once created, this module doesn't support yet bulk edition or deleting, you may find useful Commerce VBO for that purpose, but that belongs to other Tuesday's overview.

Commerce Fieldgroup Panes is an excellent module that exposes fields into the checkout process. It creates one checkout pane for each fieldgroup of the order entity using Field group module.

This is one of the easiest ways to collect information in the checkout phase, it can be used for many purposes, probably getting customer comments is the most usual, but this screencast also shows how to use information exposed by this module as data for registering users in the checkout process.

These are the basic steps to set up this module and collect information from your customers.

• Create one or several fields in the Order entity type (Store » Configuration » Order settings » Manage Fields)
• Embed those fields justs created in a new Field group.
• Access the checkout settings admin screen (Store » Configuration » Checkout settings)
• Drag & drop your fieldgroups exposed as Checkout panes to the correct Checkout pages.

Other great thing of this simple and useful module is that all the information stored in the Order entity can be used afterwards with Rules and Views, the screencast below will also show how to use this collected information for creating new user accounts.

In this screencast we'll use Drupal's built-in access control mechanisms (using the Content Access module) to grant access to premium content to users who have a "premium" role.

Here's the recipe:

• Enable Content Access and the ACL (optional) module.
• Create a role called "premium"
• Create a content type called "Premium Content" and put some great content in it.
• Verify that users can only access the premium content if they have the premium role.
• Create a product representing the premium role.
• Create a rule that grants the premium role on order completion:
  • After updating an order
  • If the order state is Completed
  • And the order contains our premium product
  • Add a role to the user who is the owner of the order

That's really all there is to it.