Date migrate generates undefined index 'timezone' notices [#1888268]

Comment	File	Size	Author
#6	date_migrate_generates-1888268-6.patch	1.14 KB	alcroito
#4	date-undefined_index_timezone-1888268-4.patch	451 bytes	kplanz
#1	undefined_index_timezone-1888268-1.patch	495 bytes	mikran

Status	File	Size
new	undefined_index_timezone-1888268-1.patch	495 bytes

Comment #2

mikran commented 3 July 2013 at 19:32

Assigned:

Unassigned

I noticed the mention over at #2034231: [META] Integrated patch for migration changes. This issue is kind of old but I should still have the migrate somewhere so I'll try to find it and provide more details.

Log in or register to post comments

Comment #3

26 September 2013 at 16:50

Status:

Needs review

» Needs work

The last submitted patch, undefined_index_timezone-1888268-1.patch, failed testing.

Log in or register to post comments

Comment #4

kplanz commented 20 August 2014 at 11:10

Issue summary:

View changes

Status	File	Size
new	date-undefined_index_timezone-1888268-4.patch	451 bytes

I have the same problem.
Attached an updated patch which works with the current 7.x-2.x-dev version.

Log in or register to post comments

Comment #5

kplanz commented 20 August 2014 at 11:14

Status:

Needs work

» Needs review

Change status.

Log in or register to post comments

Comment #6

alcroito commented 29 December 2014 at 14:05

Status	File	Size
new	date_migrate_generates-1888268-6.patch	1.14 KB

Attaching a patch that IMO is better, because instead of setting the timezone before even $return is defined, it should be set for the particular conditional branch, also making sure that if the date value is NULL, timezone should also be NULL.