Hello,

I have a problem with importing products from ubercart into drupal. I'm using the commerce_ubercart_migrate module and have been able able to import customer profiles & orders successfully. The problem is something to do with setting up the product type. I constantly see the warning message "Product type XYZ does not exist. Create it to enable migrations of this type, then go to the configuration page and click 're-register statically-defined classes.'" Whenever I set up this product type, re-register, and try to continue the import by following the "Commerce Migrate Ubercart" link (or trying again from scratch) I get the error message "Call to a member function getGroup() on a non-object in ../docroot/sites/all/modules/devel/migrate/migrate.module on line 98"

So after creating the profile type (as per warning) I continue to get the warning; so something has gone wrong here which probably results in further problems later.

The "Commerce Migrate Ubercart" link worked before the product type is registered . However, after I clicked on the "Register statically defined classes" button I continued to get the previous warning, and also an error about the "node_revisions" table not existing. It's the node_revision table that is needed if the revision check box is ticked. When I then clicked on the "Commerce Migrate Ubercart" link I got the error message "Fatal error: Call to a member function getGroup() on a non-object in /docroot/sites/all/modules/devel/migrate/migrate.module on line 98"

Any thoughts on this?

Best, Paul

CommentFileSizeAuthor
Screen Shot 2015-03-04 at 17.56.34.png183.38 KBAnonymous (not verified)
Screen Shot 2015-03-04 at 17.55.17.png139.43 KBAnonymous (not verified)
Screen Shot 2015-03-04 at 17.44.24.png164.6 KBAnonymous (not verified)
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Issue summary: View changes
Anonymous’s picture

Issue summary: View changes
Anonymous’s picture

Issue summary: View changes
Anonymous’s picture

Issue summary: View changes
Anonymous’s picture

On the Commerce Migrate Ubercart project page it mentions "If you want to map users, put the machine name of your user migration. Don't have one? Use migrate_d2d to create one." The users have already been upgraded as part of the core upgrade. Do I still need to do something here? To further clarify things: I am upgrading a drupal 6 site (with ubercart) to a drupal 7 site (with commerce). The last thing I have to do is bring over the data from the ubcerart tables into the commerce tables.

mrconnerton’s picture

@paulbooker, do your database tables (specifically the source) use prefixes? If so you will need the patch here #2274869: Problem with table prefix in the source database. That is why it is saying the base table doesn't exist.

  • Ryan Weal committed 75b08ea on 7.x-2.x
    Issue #2446075 by Ryan Weal: Fix issues when migrating from sites with...
Anonymous’s picture

I have just pushed an update to this module, which will hopefully roll a new version (7.x-2.2) which includes the changes.

Long story short, there were some bugs in the new-ish code that was detecting the product types.

More specifically: it was reporting the wrong type as missing. It then failed to create both the migration for that product and separately it failed to create the node migration for that product type as well. So when you clicked on the group it would error out because some of the migrations were connected to things that did not exist.

If your site is stuck in this condition, please download the new version, figure out which product types you were missing, create them (if only temprarily) and then reregister the migrations. Now that they "exist" they can be removed in the migrate UI, then from Drupal itself, and you can start using the migrate-register command successfully again. It will still warn you of any missing product types, but correctly now. It will no longer block you from going further.

While I was at it, I'm now having the module only return the migrations to the migrate module if the module has been successfully configured. This should prevent some edge cases from getting the white screen of death which sometimes occurs when the migration group is empty.

Anonymous’s picture

Version: 7.x-2.1 » 7.x-2.2
Status: Active » Fixed

Fixed in 7.x-2.2. Read the release notes or the comment above if your site is getting white screen of death from the 7.x-2.1 release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.