Notice: Commerce Fieldgroup Panes provides a more extensible solution to this.
This module exposes two fields associated to the order in the checkout phase for Drupal Commerce, one for author and other for comment, this way customer can add a comment to an order for providing feedback or more details.
With dreditor moving to github so has the purpose of this sandbox.
New locations are:
Utility to make requests from the Freebase API.
All the "similar content" modules out there find your similar contents based on Taxonomy.
Well, this one doesn't.
It finds your similar content based on the nodes' locations.
When you have Location module enabled, you will be able to find your similar content based on street, country or even more. And even better, this module allows you to choose which content types you want to show on each nodes' content type.
JSONfield lets you define CCK fields that map to array elements supplied by a searchable JSON data feed.
For example, if you want to reference products via a searchable JSON service (like Solr), specify the Solr endpoint URL and the object key ID that should be stored in the database. Other values from the JSON array can be used for tokenized HTML output / autocomplete selection, similar to a Node Reference.
Plinko extends the Plink theme (http://drupal.org/project/plink) and adds per path configurations for Plink.
UPDATE Sorry folks, I've been meaning to address the issues filed for this module but simply haven't had time. I'm having to bail & leave it alone for now, so if anyone else wants to take it over it's all yours.
UPDATE: This module is obsolete, as it is now bundled with the Background Process module
Make batch jobs (using the batch API) capable of running as a background process.
This module provides a few useful features for those who use the Case Tracker module and have an enterprise SLA.
Features:
- Auto assignment of tickets based on configurable role
- Auto close tickets after x days of comment and x status
- More features coming soon
Please backup database before using, this module is tested but better to be safe and sure
The aim of this project is to allow administrators to assign a userpoints category to taxonomy terms. Features include the ability to inherit the category of parent terms (default), to select whether parent terms are able to apply their settings automatically to their children, and apply a weight in case a node has multiple terms.
This module currently relies on the userpoints_nc module for the nodeapi and comments hooks.
