Unsupported

This module provides a UI for site administrators to define new Commerce Order types. Basically, what Commerce Custom Line Items is for Commerce line items. Every order type defined by this module can have different fields, display settings, permissions, etc. Every order type has its own "Create order" form.

How do I use this module?
The simplest way is via Rules. If you create a Rule that acts on the event "Before saving a commerce order", you can add an action to "Set a data value" and use the "commerce order: type" selector. Use whatever conditions you'd like to specify what type the new order should be saved as; by default, it will still get saved as a plain ol' commerce order. This works even if the user uses the add to cart form.

The other way is through code; either by implementing hook_commerce_order_presave() or custom code that calls commerce_order_new().

But why? Wouldn't it be easier to just _____?

This functionality was merged back into the main CacheTags module's 7.x-2.x branch, please focus all efforts there.

This sandbox projects contains three major changes. The 7.x-1.x branch is tracking the original project. The master branch is tracking all the changes made in this sandbox.

Here is a description of all the individual feature branches:

1. New core patch and support for tagging of the page cache

Can be tracked in the cache-inc branch, here.

Issue in the original project: #1341306: New core patch and support for tagging of the page cache

The problem with the original approach is that parts of the required functionality lives in the patch and other parts lives in DrupalCacheTags.inc which can't be included in a sustainable way. Everything needs to live in cache.inc.

Provide ads with taxonomy terms.
In such a way to find similar topics on the site and display ads that are relevant.

This project moved to Wysiwyg Grammar Checker that comes with full wysiwyg integration!

Contextual Elements provides an interface to allow administrators to add HTML elements to the headers and footers of their site given certain criteria.

The use case that spawned this module is the need to implement a Google Analytics like module that was capable of handling multiple GA codes. The filtering system was modeled from the GA module.

Installation

1. Download the Contextual Elements module and place it in your site's "modules" directory. (usually "sites/all/modules/contrib")
2. In your site, enable the module.
3. Enable permissions for the allowed roles. BE EXTREMELY CAUTIOUS! This module permits users with the proper permissions to embed ANY code into the header and the footer of the site!
4. Go to Configuration > Search and metadata > Contextual Elements to begin creating elements.

Roadmap

In future versions, I'd like to accomplish the following:

1. Store elements as entities.
2. Add default element settings for things such as meta or css elements.
3. Improve security around the headers and footers.
4. Integrate with the Context module.
5. Open an API setting to allow other modules to implement their own contextual elements.