Could not import any years in 2000 range from csv field [#2349139]

First of all thanks for this module, it's a life-saver! But I ran into a weird problem when trying to import csv data into nodes; in several thousand rows with 4-digit numbers in the 'year' column, any year starting with 2 was not imported but was populated by the default ('now') value. No amount of tampering made any difference, and all years prior to 2000 worked fine. Because of time constraints I did not go so far as to try changing the contents of the original csv column to full date format; I ended up using a text field instead, since it really wasn't essential that this 'year' field be a date, and that worked perfectly. But I do have an abiding curiosity as to what might have caused this glitch, if you have any insight.

Comments

Comment #1

twistor CreditAttribution: twistor commented 3 October 2014 at 08:35

Status:

Active

» Postponed (maintainer needs more info)

What kind of field were you trying to import into?

Comment #2

agerard CreditAttribution: agerard commented 6 October 2014 at 15:36

I tried every date type available. And although I thought I could get by with a text or even integer instead (integer import worked fine) it remains a problem, because I realized I will need to filter by date range, and though I can do that with the integer import, the view filter widget labels for dates are somewhat more appropriate for users. All I have for import is the 4-digit year, though I can of course pre-process that in some way. I just tried a sample import using iso date and altering all "2000" dates to "20000101" - they're imported as 1970! and 20020101 is ignored, becomes the current year. This is just bizarre. Would really appreciate any suggestions.

Comment #3

agerard CreditAttribution: agerard commented 6 October 2014 at 15:49

Hey, I found a workaround, I think - replacing all years in the 2000 range with YYYY-MM works for iso date import, year-only granularity. So until/unless a fix is found, at least maybe this helps....