An error occurred. Some or all of the migrate processing has failed.
Please continue to the error page

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=11&op=do StatusText: OK ResponseText: Fatal error: Class name must be a valid object or a string in .../phpbb3d7.dev/sites/all/modules/migrate/plugins/destinations/file.inc on line 563

apache log is the same:

[Sat Sep 29 17:13:17 2012] [error] [client 127.0.0.1] PHP Fatal error: Class name must be a valid object or a string in ...phpbb3d7.dev/sites/all/modules/migrate/plugins/destinations/file.inc on line 563, referer: http://phpbb3d7.dev/batch?op=start&id=11

media module is installed and enabled.

Comments

marktheshark’s picture

Same here (with media module enabled)

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?render=overlay&id=690&op=do StatusText: OK ResponseText: Fatal error: Class name must be a valid object or a string in C:\xampp\htdocs\drupaltest\sites\all\modules\migrate\plugins\destinations\file.inc on line 643

JeremyFrench’s picture

Status: Active » Fixed

I've just pushed a potential fix for this. If it could be tested that would be great.

marktheshark’s picture

I can give it a try tonight.

challenge’s picture

I wasn't at home these days and now I see a lot of fixes.

I'll try them today and report in each thread.

thanks

challenge’s picture

Title: Error 200 Class name in file.inc. Can't start migrating attachments » Error 200 Class name in file.inc. Can't start migrating attachments with media module
Status: Fixed » Active

I tried your latest dev. ( double checked that media module was enabled)
error is still there

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=53&op=do StatusText: OK ResponseText: Fatal error: Class name must be a valid object or a string in /home/quickstart/websites/phpbb3d7.dev/sites/all/modules/migrate/plugins/destinations/file.inc on line 563

no attachments imported.

BTW sorry if I didn't say it before, I'm using media 7.x-2.0-unstable6 and tried too with media 7.x-2.x-dev (2012-Oct-07).
I didn't try it with media 1.0!

Is module compatible with media 1.x only?

migrate is 2.4 stable and all modules updated to their latest stable releases, except media2.

marktheshark’s picture

I'm using Media 2.x-dev, for the record.

challenge’s picture

ok, now I tried this with media 7.x-1.2 to see if it would works with that, but there is still the same identical error, same file, same line as my last post.

So I tried on media
- 7.x-1.2,
- 7.x-2.0-unstable6
- 7.x-2.x-dev (2012-Oct-07).

None works, always same error.

BTW media1 is feature freezed and media2 is the future. :-)

JeremyFrench’s picture

Weird I am sure I got rid of that error locally. Will try and fix again.

JeremyFrench’s picture

Status: Active » Fixed

I have updated the module. Can't get this error any more. Not 100% working with media but that is handled elsewhere.

Status: Fixed » Closed (fixed)

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