Closed (fixed)
Project:
Migrate
Version:
7.x-2.2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
20 Sep 2011 at 16:03 UTC
Updated:
9 Mar 2015 at 17:58 UTC
Jump to comment: Most recent
Comments
Comment #1
mikeryanAfter 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?
Comment #2
Anonymous (not verified) commentedNo 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.
Comment #3
mikeryanAre 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?
Comment #4
Anonymous (not verified) commentedUnfortunately, 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.
Comment #5
q0rban commentedI ran into this as well on 6.x-2.2.
Here's how it happened for me.
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.
Comment #7
Ken Ficara commentedSomewhat 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.
Comment #8
dkinzer commentedI was getting this same error in a 6.x site before I upgrade the autoload module to 6.x-2.x