Bundle not set when importing data through content_migrate. [#1802310]

I'm running content migrate to import my data, then checking that data, and the bundle property in the field table isn't set. It looks like the code is there to set this field, but it's not working because it's using an expression that's set twice. (see content_migrate.admin.inc's _content_migrate_batch_process_migrate_data() for what I mean).

Attached patch removes the non-working first addExpression call, which fixes the problem.

Comment	File	Size	Author
	cck-bundle_not_set_on_migrate.patch	647 bytes	rbayliss

Comments

Comment #1

charlie-s commented 6 August 2013 at 19:35

I've already upgraded a lot of content and now see this problem. Is it an issue to have the bundle not set?

Comment #2

rbayliss commented 6 August 2013 at 21:59

It can be later on if you need to access the data with views or something. IIRC, when I was seeing the issue, it was causing content not to show up in certain places. Luckily, it's pretty easy to fix later if you need to (just look up the node type for each entity_id in the table that's missing a bundle).