This module demonstrates a way to create Google Gadgets from within Drupal.
It is expected that users will actually evolve it to a generalized gadget creation class, from which actual gadgets will be derived without having to create a module for each gadget.
It requires PHP5 and the DOM extension.
This module builds upon the CollectiveAccess module, to allow retrieving data from CollectiveAccess and importing it into Drupal nodes (or other entities) through the Feeds module.
Defines a field formatter to display a link to an image as an HTML image element.
The Imagecache External module (D6 only; http://drupal.org/project/imagecache_external) is recommended to allow for custom dynamic external image manipulation and cache.
Integration of the spriteme.js of spriteme.org
Doesn't work with current versions of Drupal Commerce. New maintainer required, as I won't be supporting this module, until I need it again.
This adds payment icons to the payment pane for Drupal Commerce.
Processors supported are Authorize.net, Paypal WPS and Paypal WPP. More are very easily addable in code. I will not be adding a user interface for this module, but patches are welcome, if you want to make one yourself.
This module tracks, by Ajax, how long a registered user took to read a page and the amount of time he spent on the entire site.
You can configure which content type and role should be tracked and view the report, exhibiting the total hours (or minutes/seconds) a user spent reading a page and at the entire site.
This module just track node pages and registered users. Taxonomy or views pages aren't tracked, but can be if the code is edited.
If you need to track anonymous visits, consider using Google Analytics (GA can't track registered users by its privacy terms).
This module seeks to add reporting to the Drupal Commerce module, similar to the reports found in Ubercart. Commerce Reports will use the Views 3 module.
I am actively seeking co-maintainers that are knowledgable in the area of modules, Views, and the Commerce APIs.
Somewhat based on the Matrix module. Taxonomy Matrix is a bridge between taxonomy and a CCK Matrix field. It can be used to create a matrix of selections based on 2 selected taxonomy categories.
Using CCK, add a new Taxonomy Matrix field. The admin interface will ask you for the category to use for row headers, and the category to use for column headers.
Colors & Patterns would give you something like this:
This is an API module to help putting entities in a tree hierarchy. (Actually. DAG. I want to support multiple parents). We encode trees by enumerating each children of a parent, encode them with UTF-8 (I just use it as an algorithm) and then writing them down as an encoding of the materialized path. As UTF-8 as a binary stream sorts the same as the numbers encoded this works well. UTF-8 can encode at most 2**31 so that's the most children each parent can have.
MySQL indexing restricts us of somewhat to a max depth of 255 (or less) but that's not serious.
This module integrates the Constant Contact module with the Webform module.
It provides a Webform component called "Constant Contact Email" to enable you to add and remove subscribers to and from your constant contact mailing lists using a form built by webform.
