This module provides some tools for planning courses in a school context. As a bonus, it also provides a library for sharing learning resources.

Overview

Commerce Quotes is a module for Drupal Commerce that will allow users to send a request for quotation (RFQ) instead of placing an order during checkout. The module provides a number of methods to determine whether an order should become an RFQ. Conditions might be that the order contains products without a price or that the customer checked a box indicating he or she would like to place a RFQ during checkout. Alternatively you can specify your own conditions using the amazing Rules module.

Shop administrators can get an overview of all incoming RFQs from where they are able to send an altered version of the RFQ as a quote back to the customer. The customer then receives an email notification after which they might accept or decline a quote. Once accepted an order is placed and normal checkout will be resumed.

Features

• Customer overview pages. (pending RFQs and accepted and declined quotes)
• Admin overview page. (incoming RFQs, drafts, sent and declined quotes)
• Customers can accept or decline quotes.
• Optional checkout pane where customers can choose to place an RFQ instead of an order.
• A number of example rules.

Provides Drush commands to upgrade Content Profile content types into either fields on the core User entity or Profile2 profile types. All functionality is available via drush, there is nothing added to the website's admin UI.

A replacement for date_ical + calendar. More features, simpler to deploy.

Depends on views and date_api.

This module is an extension of Drupal Commerce that provides a display formatter for the Commerce Price field in which you can specify the decimal places are displayed.

The sales pitch

Do you use a node for your 404 page?

Do you hate how translating the node behind the 404 page (or 403 page, or front page) doesn't actually work the way you'd think it would? By default, everyone will see the 404 page you configured under Site Information by default. To show translated versions for other languages, you have to turn on the Internationalization Variable submodule from the Internationalization module. You then have to tell it which node to use for each language where it isn't the default-language node.

UNTIL NOW!

Internationalization 404 leaps into action just before your 404 (403, front) page is served and changes it to the translated version instead.

But wait, there's more! It actually checks to see if you have configured a different node with the help of the Internationalization Variable module, and respects that setting.

This module was developed because featurizing variables containing node paths didn't seem like the way to go. If we already have translated content, why should we also have to translate the variables? We only need to know the source node, and there is less chance for human error in configuring that.

Installation