This module was adapted by Bojan Živanović (email: bojanz@gmail.com) @ http://vividintent.com from the original Affiliate module by jhuckabee.

Originally multiple people wanted to pool together and sponsor this module. No one followed through unfortunately so if you'd like to support continuation of this module and add features, please email bojan and then continue this increasingly important module.

This new and improved affiliate module has the following features:

Granular tracking
-User based tracking
-Role based tracking

Ability to create affiliate links:

Here is a unobtrusive version of an ajax cart.

* Got a new block called 'Ajax Cart'
* Use standard theme functions for cart
* Without javascript enabled , the cart hold functionality

Version 0.5

* Fix some minor issues

Version 0.4

* Small Javascript Bugfixes

Version 0.3

* Add new options

This module allows you to map a node type to an Ubercart product. When a user creates a node of that type, the specified product is added to the shopping cart with a node reference to the newly created node. Options in the module allow you to turn links in the shopping cart into edit links for the node, display a summary of the node details in the shopping cart and on the order screens, and hide CCK fields on the node type from users who don't have the "edit content" permission. This makes the module an ideal candidate for registration site and customizable product sites that contain additional fields only administrators should have access to when processing the orders.

Sometimes you want to list products in the catalog but you don't want people to buy them. This module lets you disable the price and/or "add to cart" on a per product basis. Works in the UI the same as the shippable product checkbox.
Test on a development site first.

This is a blatant, unashamed edit of uc_roles, with my thanks for the fine module to rip apart. The intent of the edit was to handle node publication in exactly the same manner as role asignment. Node poduct and node expiry tables are created, and the module syncs with the scheduler module. Not sure if this is necessary, but most who deal with node expiry seem to be using it.

This module appears to be working, but it needs EXTENSIVE testing. Please do not rely on it yet. The code is in rough shape, and I upload it so other, more experienced eyes can tell me where I have gone wrong.

UC Restrict Qty lets you add a very basic Restrict Qty. product feature to products in your Ubercart store to limit the quantity of those product in the shopping cart to 1. This is useful for single purchase products or for instances where it just doesn't make sense for a customer to purchase more than one and you want to prevent it from happening.

Due to the way products are added to the cart, customers can add multiple variations of the same product to their carts (i.e. different attribute/option combinations) but never more than one of any given variation.

UC Node Access lets you attach Node access features to products in your Ubercart store. These features allow customers who purchase the product to receive view access to nodes on your site either indefinitely or for a limited time based on the feature's settings. UC Node Access does not handle access grants itself but rather depends on other modules to define handlers that integrate UC Node Access with the various node access modules developed for Drupal.

Currently integrated node access modules include:

Project page on drupal.org: 
http://drupal.org/project/uc_node_access

This module allows you to specify a maximum amount of characters that a text attribute can have. One example is if you are selling jerseys and want to limit the name on the back to 15 characters and the number to 2.

The size of the attribute textfield will default to size='max chars' but can also be configured to be set to a certain amount of pixels * max chars.

uc_event turns an event content type (from the event module) into an Ubercart product. Only one node is created but has attributes of both content types, that is it appears in the event calendar and can be added to the shopping cart. Product attributes were trimmed to include only those necessary for an event. The admin area includes an option for creating content types other than the default 'event' content type as paid events.

Ever needed to customize a product?
Wanting to calculate setup-cost, administration fees, film-costs, mould costs, or whatever?
This module intends to do so. Every product will have a price + a base cost. Every attribute will have a base value too. Need to calculate something like:

Cap: $3 * qty
Setup: $10

Print 1colour: $1 * qty
Setup 1 colour: $10

Your total will be: $40 for 5 pcs and $60 for 10 pcs.