After installing Migrate (along with Migrate UI, Migrate Extras, Profile2 and WordPress Migrate), I attempted to navigate to /admin/content/migrate, but the page came up blank. In php-errors.log, this error was logged:

[20-Sep-2011 08:32:12] PHP Fatal error: Class 'MigrateGroup' not found in \sites\all\modules\migrate\migrate.module on line 89

This is in Drupal 7.7 .

Please let me know if you need more info and I will be happy to do further testing.

Thanks for all your work on this useful module!

Comments

mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

After deploying the 2.2 code, did you run update.php (or drush updatedb)? If you clear your cache (drush cc all), does that fix it?

Anonymous’s picture

No luck. update.php returned "No pending updates". I did run "drush cc all" and drush successfully cleared all caches, but I'm still getting the error on /admin/content/migrate.

mikeryan’s picture

Are you sure you've fully installed 7.x-2.2? I can't see how MigrateGroup would not be defined - in the .tar.gz file, includes/group.inc is present and is referenced in migrate.info, can you verify that's true in your installation?

Anonymous’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Unfortunately, another person has significantly changed code on the site I am working on and I can no longer provide consistent troubleshooting information. (I can confirm that includes/group.inc is present and is referenced in migrate.info). My best guess is that this error was due to a misstep on my part in installing the module. I apologize for the inconvenience.

Thanks again for your work on this very useful module.

q0rban’s picture

Category: bug » support
Status: Closed (cannot reproduce) » Fixed

I ran into this as well on 6.x-2.2.

Here's how it happened for me.

  • I upgraded Autoload module to 2.1
  • I ran drush updb
  • I created a new migration and enabled it
  • I enabled migrate_ui, navigated to /admin/content/migrate
  • I see "Class 'MigrateGroup' not found".

I then ran drush updb, and lo and behold, another Autoload update was there for me to run. Strange! Once I ran that update, everything started working as expected. I don't know if the update failed the first time or what, but thought this information might be useful to someone else.

Status: Fixed » Closed (fixed)

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

Ken Ficara’s picture

Somewhat irrelevant comment for searchers who come upon this page ... some distributions (eg, OpenPublish) install autoload 1.4. This error always occurs with that version of the module. If you're seeing this error, make sure you're on 2.2 (may need to disable, delete and reinstall), clear cache, update, and it should work.

dkinzer’s picture

Issue summary: View changes

I was getting this same error in a 6.x site before I upgrade the autoload module to 6.x-2.x