Closed (outdated)
Project:
Feed Element Mapper
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2009 at 18:49 UTC
Updated:
15 Aug 2020 at 08:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
socialnicheguru commentedI have this too.
In my case I am using an XML feed and the date is the import date not the event date.
I used date and time as no others worked.
UPDATE:
MY DATE IS A NOT A CUSTOM DATE FIELD, but a regular one.
the start date is the date that I used feed to start the feed.
The end date is the start date.
This is just weird.
Comment #2
mediahackers commented+1
Comment #3
antianti commentedWe solved the problem in this way!
Comment #4
alex_b commentedThis approach could work, but I'd need to better compare it to the other mapping options, maybe a person better aquainted with date mapper than I could have a look at this.
Basically this customdate option can parse anything that can be parsed with strtotime() while ignoring time zones, right?
Either way, this patch will need work as it does not adhere to coding standards: http://drupal.org/coding-standards
Comment #5
avpadernoI am closing this issue, which is for a not-supported Drupal version.