When I tried running the content migration on a video embededd media field, I got the following error:
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=127&op=do StatusText: Service unavailable (with message) ResponseText: MediaInternetNoHandlerException: Unable to handle the provided embed string or URL. in media_internet_get_provider() (line 269 of .../sites/all/modules/media/modules/media_internet/media_internet.module).
This wasn't enough information to figure out the problem for me, so I borrowed some code from this issue and replaced line 269 of media_internet/media_internet.module with a call to watchdog including the embed string that was breaking:
function media_internet_get_provider($embed_string) {
foreach (media_internet_get_providers() as $class_name => $nothing) {
$p = new $class_name($embed_string);
if ($p->claim($embed_string)) {
return $p;
}
}
// throw new MediaInternetNoHandlerException(t('Unable to handle the provided embed string or URL.'));
watchdog('video field', "Unable to handle the provided embed string or URL: " . $embed_string);
}
The migration now worked because it tossed the error into the log with more information ("Unable to handle the provided embed string or URL: http://vimeo.com/38264099"). I realized I was missing my Media: Vimeo module. I installed it and the migration worked fine.
I'm mainly posting this issue in case people run into this error and can't find any related issue when searching drupal.org, but I posted it as a bug report because it might be there would be a way to handle this error better. Feel free to move the issue if I've filed it unhelpfully.
Comments
Comment #1
Edgar Saumell CreditAttribution: Edgar Saumell commentedSame happened here. Installing media_youtube and media_vimeo solved it for me.
Setting priority to critical since this don't let you upgrade between versions.
Comment #2
scottybrookie CreditAttribution: scottybrookie commentedThis worked for me too, with one caveat.
Installing and enabling media_youtube and media_vimeo solved the problem for all but one node. The last node, which was holding up the whole migration, turned out to have a link to a YouTube video that had been made private. I deleted that one node, then the migration was successful.
Comment #3
ShaneOnABike CreditAttribution: ShaneOnABike commentedOh snap! Same happened to me whereby the videos had been removed. THat's somewhat annoying and I wish there was a cleaner fallback then just not allowing the migration.
Anyway, for those who need to better understand what to do...
Simply go to yoursite.org/node/xyz/delete specifically for the outlined entity ID's that have issues.
This will allow you to remove the entity/node and then rerun the migrate.