Karen,

The folks working on Node_Import module are having a tough time importing date values into your date fields. That issue is here:
http://drupal.org/node/374346

Part of the problem is with the Node_Import module not being able to import values into a field where the widget is not set to "select list". They are working on that but if you have any insight that would be awesome.

The other issue is the question is what format should date values be originally created so that they are more likely to import into the date fields? Are we talking 02/22/2009 or 2-22-2009 or 2/22/2009T18:30:00 or such? What's the safest bet?

Thanks for the help!

Comments

karens’s picture

karens commented
Status: Active » Fixed

I always recommend using node_save() instead of drupal_execute() because drupal_execute() is horribly fragile and breakable (and there are known bugs). Even Jeff Eaton (one of its creators) suggests being really careful about using it. I did a whole long thread on all the problems it creates when trying to fix brokenness in Content Copy (which was using drupal_execute()). If you use node_save() you don't need to know anything about the widgets, you just import data in the format the field expects -- YYYY-MM-DD HH:MM:SS for datetime, YYYY-MM-DDTHH:MM:SS for ISO and 9999999999 for Unix.

I'll post the same info on that issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

doublejosh’s picture

doublejosh commented

On the topic of date imports...
I just ran a node import with the "Date" widget (among the three field options) with the ISO format mentioned above "YYYY-MM-DDTHH:MM:SS" and it seemed to scramble all the times.