I'm having some difficulty with trying to get dates for Ongoing events imported with the correct start and end time From Evanced.
I've got data coming in from our feed and some fields are matching up in the XML Mapper but it looks like the date field input format is not correct.
Mapped Elements
title = Title
description = Body
date1 = Start and End Date (Date)
time = Start Time (Date)
endtime = End Time (Date)
enddate1 = Start and End Date (End Date)
blank = Start Time (End Date)
blank = End Time (End Date)
id = Evanced ID
EXML fields
Gallery Event
Monday, July 16, 2012
4
2012/07/16
201207160000Gallery Event
2012/07/20
Output in node
Date
July 20th, 2012 (All day)
End Date
July 20th, 2012
Evanced ID
4
I can't figure out why both the to and from values in the "Date" field are coming up 2012/07/20 as well as the "End Date" field value is 2012/07/20. When the start date is 2012/7/16.
Also, I'm trying to figure out the correct input format for the date field to recognize the incoming dates from Evanced. How do you set the hour fields?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | multiple_date_fields_fix-1687840.patch | 6.08 KB | slanger |
Comments
Comment #1
slanger commentedThank you for turning your original comment into a new issue, jgoodwill01.
I was able to duplicate the problem you reported and am working on a fix for it. My hope is to post a patch in the next day or two. An answer to your other question should be forthcoming as well.
Comment #2
slanger commentedHi jgoodwill01:
Please apply the following patch and let us know whether it corrects the problem.
I hope I'm not misinterpreting your second question. Below is my best attempt to answer it:
Ongoing events in Evanced are never assigned start and end times -- only dates. When an event is imported into Evanced without a start and end time, both times are automatically set to "12:00am" in the event node, which the Calendar module recognizes as an "All Day" event. In the EXML feed, if the "time" and "endtime" elements are assigned values, then those will be used instead.
Comment #3
jgoodwill01 commentedI believe this corrected my issue. Thanks!
Comment #4
slanger commentedTerrific! Thanks for reporting back. I'll fold this change into the next release of the Evanced Events Importer.