Commerce Migrate Ubercart is a migration using Commerce Migrate and the Migrate suite that can migrate 6.x and 7.x Ubercart stores from either the existing Drupal database or a remote database.
Visit admin/content/migrate/ubercart_migration_options to configure import options, including the source database and filesystem locations.
Please read the README.txt. There are specific requirements for setup before a migration.
What currently works:
Product types are created from ubercart product classes.
Each product type gets its own migration.
Product image migration.
Each product type gets its own node migration, which creates the matching product_display nodes.
Customer billing profiles are created from the billing info of each ubercart order.
Orders (and line items) come through.
What doesn't work yet:
Attributes
Taxes
Handling the case when the target product type / sku that we're creating already exists.
There are a number of things that will never be able to be addressed, as with all migrations. Every migration will require review and work on the migrated store.
This module provides an additional table-like style to views that allows administrators to indicate that only some fields (columns) should be rendered by default but the user should have the abilit
At the moment I have developed two versions. Version 1 (7.x-1.x) was based on the old payment system from Mercado Pago (to be deprecated) and version 2 (7.x-2.x) for the newest API.
Provides an autocomplete FAPI element, basically an enhanced version of a textfield with autocomplete, with the benefit of hiding away the real record ID. It allows the user to search and select an appropriate record as normal but uses a hidden field to store the selected record ID.