Closed (duplicate)
Project:
Feeds
Version:
6.x-1.0-beta10
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2010 at 17:12 UTC
Updated:
26 Sep 2012 at 23:17 UTC
Looked for an issue on this but didn't find one...
While running .csv imports, the importer is changing the time on my imported nodes to GMT from EST.
I've double checked my server time settings (correct) my site time settings (correct) and checked the CCK date field, which is set to use site time.
I updated to beta10 yesterday, hoping to fix the issue but still all the dates are being automatically changed. I've been using the same setup, same files for 6 months and this is the first time I am seeing this issue.
Thanks
Comments
Comment #1
mudsurfer commentedI have same issue: I'm new to feeds and have spent last 5 days, desperately trawling through all sorts of online resources, looking for for a solution. I thought I was not configuring Feeds properly.
My users need to import a CSV file into nodes, which include a CCK date field with from and to date and time, with granularity down to the minute. My users and the site are all in the Melbourne Australia timezone (currently AEDT (Daylight)time - +11UTC). Server is hosted in US.
Need to import approx 200 nodes at a time, every month or so.
After many aborted attempts, I have finally reverted to creating an Excel based converter: My process is clumsy, but at least at the moment it's working: user enters the date/times in excel - excel converts to UTC via a formula, the appropriate comma delimited formated is down via a concatenate formula, and then user cuts-and-pastes this into text-pad, saves as UTF-8 format, and uploads to drupal via Feeds.
End result (currently!) is that the cck field in drupal is populated with the same date and times as was originally populated in the excel spreadsheet....
I wish I knew enough about PHP to make drupal do all this, I suspect there is some parsing and formatting processes that I could do it all in Drupal rather than excel - but at the moment this is what I have.
And it's still far better than loading 200 nodes by hand!
If anyone has the "proper" solution, I'd be very keen to understand and implement.
Comment #2
ow1n commentedThis is still an issue. If anyone has come up with any workarounds I'd love to hear them.
Comment #3
mudsurfer commentedow1n: still an issue for me, but only workaround I have come up with is manually adjusting the required times external to drupal before uploading them. Not good - but at least workable.
Comment #4
hanno commentedsee also #722740: Feeds Date mapper converts imported dates to GMT unless in UNIX timestamp format
Comment #5
twistor commentedClosing this as a duplicate of #722740: Feeds Date mapper converts imported dates to GMT unless in UNIX timestamp format.