Forum Replies Created
-
Posts
-
Andras,
Miraculously, starting just this afternoon, all of our imports started working again. They had been failing since the April 17th or perhaps earlier since that’s as far back as the history log shows. At this point, I consider the issue resolved and will open a new ticket if the issue shows up again.
Dan
Jaime,
Sorry for the long delay getting back to this. Changing the end-of-day cutoff was successful in preventing the all-day events from gaining time. Those events now retain the expected values. While we have some events that cross midnight, it’s not worth having other events become multi-day events.
Thanks for sticking with this.
Dan
Jaime,
The event that had been added was for this past Saturday (20th). I’ve added a couple of new events (one on Jan 27th, one on Feb 3rd, both titled “Saturday”). After they were added, I ran an import and both came in as expected. After another update/import, they were now showing as multi-day (Jan 27-28 and Feb 3-4, respectively). This is true for both front-end and back-end.
The “End of day cutoff” is 2:00 am.
Also sending the system information as a private reply.
Thanks,
DanJaime,
I added a new event (titled Saturday) to the Google calendar and made sure it had the correct timezone. I imported it via EA, and it imported as expected and showed correctly on both the front-end and back-end. I verified that the timezone in the back-end shows as “America/Chicago”. Upon re-import, the event still gains time. Now on the front-end it shows the event occurring January 20-22. On the backend, I see the same thing, the event start/end as 2018-01-20 to 201-8-01-22.
Dan
Jaime,
Thanks for your work on this.The Google calendar timezone setting is set to “(GMT-06:00) Central Time.”
The Import settings are actually set to Status: Published.
Update Authority is currently set to “Import events but preserve local changes to event fields.” If I choose “Do not re-import events. Changes made locally will be preserved” I don’t see the problem but we also don’t get updates to the events, which is important to us.
Under Settings > General, the Timezone is set to “Chicago” but I’ve also tried UTC-6 with the same results.
After the initial import, all imported events have the correct date, time, and timezone set. However, each subsequent (scheduled) import is changing the end day/time of my events. I have several all-day events and each time, the event gains 18 hours (from what I can see in the _postmeta table).
After the 2nd import, the event that is on the 16th suddenly shows as starting on the 16th and ending on the 17th (although it’s still considered an all-day event so the actual end-time isn’t displayed, just the date). After the third import, the event will show starting on the 16th and ending on the 18th. Each import keeps adding a day to the end.
Jaime,
Thanks for the suggestions and next steps. I’ve updated all of the plugins and created a calendar with test events and the issue still occurs. All-day events gain time ( 18 hours each time the import runs ).The test calendar that I’m using can be found at https://calendar.google.com/calendar/ical/stolaf.edu_7kninpd6ibhg55o74bv1e5d9m0%40group.calendar.google.com/public/basic.ics
Andras,
Thanks for your help. If I run the stuck ones, they run and complete as expected. I also installed the latest update for the Events Calendar and Events Calendar PRO and the behavior has changed. It appears that the jobs are running — at least that is what the Schedule Imports and History tabs are showing.For the time being, I think we can wait a day or so to see if that continues or if the problem reappears.
