[Marco]

Just an update:
I’ve deleted and re-imported each of the three feeds I use several times:

First feed I had to delete, clear cache, import, 3 times. 3rd time it imported with the correct time.
Second feed worked first time.
Third feed took 5 attempts.

I now have all the feeds displaying the correct time again but I’m not sure why it took several attempts at deleting and re-importing and I’m wonder if when it runs nightly updates if it will ‘break’ again.

Regards,
Marco

[Marco]

I’m waiting for confirmation from all parties involved but this looks like it did the trick! At least as far as I can tell 🙂

Thank you so much, András!!

[Marco]

András,

This wasn’t able to solve my issue.

It fixed the time, left the timezone as UTC, but now “All Day Events” extend to two days instead of just the day they’re supposed to be for.

Regards,
Marco

[Marco]

Hello,

I followed the instructions and changed those last lines:
modify_imported_event_timezones(
‘null’,
‘America/New_York’
);

…entered the full file into functions.php
…deleted all imported events
…re-ran the imports

Same problem 🙁 Everything is still in UTC.

Regards,
Marco

[Marco]

Hi András,

Thank you- I will try this out. Can you tell me where I put this code/file?

With regards to the first part of your message; I’m not able to edit the incoming feed.

Regards,
Marco

[Marco]

Jaime,

This is still importing the events as UTC. Is there another step I’m missing?

As in, events that are not all-day events have the time listed in UTC.

Regards,
Marco

[Marco]

Hi Jaime,

Respectfully, I disagree: This is not working as intended and this is not a solution. The feed I gave you is one of many feeds — we have a very large number of events impacted over the next year and they are constantly being added. I can’t go in and manually adjust every single one, that’s why we purchased the event aggregator.

More to the point, “all day” events are not coming through in UTC. No timezone is mentioned.

This is the event from the feed:

BEGIN:VEVENT
DTSTAMP:20171205T152937Z
UID:event_4850_20171211@[Removed]
DTSTART;VALUE=DATE:20171211
DESCRIPTION:[Removed]
SEQUENCE:20871549
SUMMARY:[Removed]
END:VEVENT

The DTSTART Value is only a date. Unlike other events that have a specific time and indicate they are UTC (DTSTART:20171207T130000Z for example, the Z after T string indicates UTC) this is only saying it is an all day event for 20171211 and does not indicate a time or timezone and that date should be honored as an all day event on the local timezone.

Regards,
Marco

[Marco]

This reply is private.

[Marco]

Hello,

1. How could I put in a suggestion to have this changed? Conceptually I still believe this is wrong and not as intended: When using a shortcode to embed the calendar somewhere, I believe the user experience shouldn’t change from where it was embedded and if it does, it somewhat negates the point of using the shortcode.

2. Great! Thank you. Is there a public bug list that you could send me the link for this particular item so I can track it?

Regards,
Marco

[Author]

Posts