Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • As a quick addition … I looked at the main blog’s calendar for this site and it is behaving properly. This is indeed a sub-blog issue .. I’m not sure how that helps debugging .. but there you have it.

    I’m not sure if this is specific to the nottsforestsoccer ics file (mentinoed above) .. but I think I can explain what the problem is, and hopefully Marcus can come up with a solution .. either in the code or specific to that blog ..

    The times are entered as Pacific .. and they show up just fine on the calendar. In the ICS file, the the DTSTART and DTEND are *supposed* to be converted into Zulu time .. and while they do have a “Z” on the end of them, the timestamp is still Pacific .. (Note: its actually an hour off as well, no doubt a daylight savings issue where its recording PDT instead of PST or vice versa) …

    The point is .. when Google Calendar (or anything else) reads in the file, it *thinks* it is in Zulu/UTC/GMT time .. but the stamp is not being adjusted to that time when outputted to the .ics file.

    Example:
    An event happening May 23rd @ 5pm Pacific has a
    DTSTART:20120523T180000Z

    (Which is 6pm) … clearly not the Zulu time … which should be… if I’m not mistaken … 6hrs later (thus 7hrs ahead of the original time [GMT -7:00])
    So .. something like
    DTSTART:20120524T000000Z

    So, is it the individual blog’s fault that the timestamp isn’t properly being converted to Zulu .. or is the plugin?

    Will this be fixed in the next update? It would be wonderful if at least the demo site [https://demo.wp-events-plugin.com/events.ics] could pass validation at: https://severinghaus.org/projects/icv/

    As it stands now .. Google Calendar rejects the feed.

    Thanks for all your work on this!

Viewing 3 replies - 1 through 3 (of 3 total)