Unsupported

Concept

Imagine that a new version of your favorite distribution is released. What if all you had to do to upgrade an existing installation was to type: "drush distro update", no matter how radical the changes in the distribution's composition? Is that a goal worth pursuing?

Semantic Versioning

After releasing Distro, we found Semantic Versioning manifesto: http://semver.org/ and were pleasantly surprised to see how well our goals aligned with the thinking of Mr. Preston-Werner. We will try to keep an eye on the progress of Semantic Versioning and adopt its best-practices when possible.

Description

Distro is a client/server tracker to manage modules and features that make up a Drupal distribution. While features are used to encapsulate distribution functionality, and an installation profile is used for initial installation of a distribution, "distro" does the remaining part: things necessary to easily maintain an up-to-date distribution installations.

Near-Future Goals

Full support of Features, integration with Drush, integration with Aegir.

See Distro in action, used by following distribution(s):

http://tattlerapp.com
http://openpublishapp.com

Requirements

Update (August 2012):

This module is no longer being developed. All focus has moved to the new Authorize.net API module and it's companion Ubercart Authorize.net Payment Gateway module.

The 6.x-1.0-alpha1 release of this module represents that last "stable" release. The 6.x-1.x branch is considered UNSTABLE! It might work, but there are no guarantees. We started reorganizing this module in the 6.x-1.x branch, but ultimately decided a new module was needed.

Overview

This module enables advanced functionality for the Authorize.net payment gateway, based on their Customer Information Manager (CIM) system. With it you can store your customer's credit card information on Authorize.net's servers. This makes several important features possible, without exposing a store owner to the security risk of storing credit #'s in their database.

You'll like this module if you want to:

• Help your repeat customers checkout more quickly by entering their credit card info only once.
• Accept pre-orders for a product and charge the customer when you ship it.
• Process recurring payments using the uc_recurring module.

This module can let user mark their own favorite nodes that they love !!

GOAL
- integrated with view
- favorites tab on user profile
- ajax button "add to favorites"

For use during data migrations from other systems, this module allows you to "re-key" comma-seperated-values data imported from other sources.

Use the node import module to import your data as text fields. (The node reference and content taxonomy import fields in node reference require primary keys that are drupal nids, which my spreadsheet does not know about on import.)

If your data has comma-separated-values lists that correspond to a "primary key" of another column (such as a SKU, ISBN, Record ID, etc), you can use this module to explode those comma-separated-values and have their Primary Key looked up from the import source. Then, the module will stuff a node reference or content taxonomy field with the nid or tax term that was referenced in your imported csv data.

The module uses batch api to run the operations.

If you have a large migration requiring translating many fields, you can easily write a function to invoke a batch once for each of your cck conversions. The script below takes approx. 1 hour to run on a modern web server:


function execute_dsc_migration() {
// This temporary method runs the DSC product migration/rekey operation as a batch

$operation_type = $target_cck['type'] == 'content_taxonomy' ? 'content_taxonomy': NULL;

$batch = array(
'title' => t('Re-keying CSV Values to References'),
'operations' => array(