Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
These notices are generated with and without timezone argument.
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 |
Comments
Comment #1
mikran CreditAttribution: mikran commentedComment #2
mikran CreditAttribution: mikran commentedI 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.
Comment #4
kplanz CreditAttribution: kplanz commentedI have the same problem.
Attached an updated patch which works with the current 7.x-2.x-dev version.
Comment #5
kplanz CreditAttribution: kplanz commentedChange status.
Comment #6
alcroito CreditAttribution: alcroito commentedAttaching 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.
Comment #7
mikran CreditAttribution: mikran commentedComment #8
joelpittetFixes the notices, thank you.
Comment #9
ohthehugemanatee CreditAttribution: ohthehugemanatee commentedworked for me, too. I still have other issues when the imported date is unix 0, but that's a separate issue. Seems RTBC.
Comment #10
ayalon CreditAttribution: ayalon commentedThanks! Tested and working! Please commit it.
Comment #11
heddnRTBC again.
Comment #12
opiRTBC for me, #6 fixes every notices, thanks.
Comment #13
Chewie CreditAttribution: Chewie commentedPatch for Date 7.28 version https://www.drupal.org/node/2451027
Comment #14
podarok