Postponed (maintainer needs more info)
Project:
Migrate Extras
Version:
6.x-2.4
Component:
Date
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
19 Jul 2012 at 17:50 UTC
Updated:
24 Mar 2021 at 03:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedUpdate : Just rolled back to 6.x-2.3 and reimported everything. The bug doesn't appear.
Comment #2
mikeryanI assume the date field's default value is configured as the current date? And you're expecting the date field to end up empty? What if you add ->defaultValue(NULL) or ->defaultValue('') to your date field mapping?
Comment #3
Anonymous (not verified) commentedFirst reflex was to check default value of this field and it was already set to Empty. (Not by php code, but by a dropdown list)
Although, default value of the end date wasn't set to empty, but set to Same as start date.
Sorry for poor terms/english, it's not my main language and my Drupal is in french :/
I'll test furthermore later, if I change the end date to Empty.
Comment #4
jangolden commentedHi, I am also having this problem. Migrate version 7.x-2.4+28-dev, Migrate Extras 7.x-2.4. I tried both suggestions in #2, with no luck.
Default date for cck field is set to no default. Any suggestions would be appreciated!
Comment #5
jangolden commentedUpdate: I was able to get around this issue by changing the date widget from select list to pop-up calendar.
Comment #6
aldibierThe date.inc the variable $from should be validated to don't calculate timestamp if the variable doesn't have a value.
Comment #7
aldibierHere a patch to fix it, I've tested with all widgets.