So I was attempting to migrate over a bunch of events from another database in which each event had a start time and an end time. Each time I attempted to migrate the fields over, I would get a ton of errors (one for each row) telling me that the $tblinfo->multiple_separator value was not present on line 85 of content.migrate.inc. With a bit of digging I found that for some reason these datetime fields were being flagged as "multiple" value fields, when in fact, they were a single value time-stamp. So this was causing the if statement on line 84 to treat the field as a multiple value field when it wasn't and thus was throwing all the errors and never passed the values on to the rest of the migration processes. Basically, I ended up with a bunch of events with titles, summaries, locations, descriptions, etc (because everything else worked), but w/o any start/end times.

The patch below fixed the issue.. basically forced it to treat these fields as single-value when migrating datetime CCK fields. But I'm sure it's not a good fix, since it eliminates your ability to use multiple values for datetime fields, if someone ever desired to do so.

Anyway.. in short, here's the patch for anyone else having an issue with migrating datetime CCK fields. If anyone wants to look into this and fix, I'm sure it'll save someone, somewhere a BIG headache in the future.

Thanks.

CommentFileSizeAuthor
datetime_fix.patch523 bytesRavenHursT

Comments

moshe weitzman’s picture

Title: Datetime CCK field breaks migrate when starting time and ending time are used and seperator field is left empty in migrator. » Support To for Date Field

Yeah, not right fix. I think we need to allow separator like semicolon for from/to dates and then leave the usual | or other admin defined separator for multi value. Right now, migrate_extras has no support for To date.

mikeryan’s picture

Version: 6.x-1.0-beta1 » 7.x-2.x-dev
Status: Active » Closed (duplicate)