More exception catching to prevent in failures in content_migrate [#1266842]

I had to add some more exception catching to deal with errors I get doing a large upgrade of user-generated content. Mainly I would get fatal errors preventing an entire field from migrating if one record had text that was too long, so I just wanted to catch those errors and keep migrating.

Patch needs testing as I am running on drush and not using the drupal_set_message route myself.

Comment	File	Size	Author
#2	cck-rolback_field_on_failed_data_migration-1266842-2.patch	3.83 KB	fbrooks
#1	content-migrate-try.patch	5.07 KB	Jody Lynn

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Jody Lynn

she/her

English

CreditAttribution: Jody Lynn commented 1 September 2011 at 16:32

File	Size
content-migrate-try.patch	5.07 KB

Comment #2

fbrooks CreditAttribution: fbrooks commented 18 June 2012 at 18:14

File	Size
cck-rolback_field_on_failed_data_migration-1266842-2.patch	3.83 KB

I agree that some kind of exception handling to allow it to continue is desirable, though I would take the additional step of rolling back the field in which the error occurred. See attached patch.