Recurring Events Saving Wrong Custom Recurrance Time

Home Forums Calendar Products Events Calendar PRO Recurring Events Saving Wrong Custom Recurrance Time

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #1023930
    William
    Participant

    When I add a custom recurrence rule with any time other than the checked ‘same time’ (even if I manually enter the same time), the rule defaults to either 13 or 16 hours. Before I click ‘Update’ or ‘Publish’ the rule is described as lasting 1 hour, but when I save it’s set to something like this:

    An event every 3 week(s) on Sunday that begins at 10:00 am and lasts 0 day(s) and 13 hour(s), the last of which will begin on 2015-12-10

    We’re using it for a course schedule with lots of odd recurrence rules and it’s throwing the calendar pretty far out of whack. Anything we can do?

    #1024213
    Brian
    Member

    Hi,

    Sorry for the issues here. I can help troubleshoot this with you.

    I believe we have a bug ticket in already to resolve this, but I found that when you use the custom time it uses UTC 0 time and not your timezone.

    If you follow along with my instructions here does it fix the issue for now:

    Recurring event with diferent hours

    In that case I was trying to do a 8am start time and set the time to 3am and it worked.

    Let me know if that is a work around for now.

    Thanks

    #1024240
    William
    Participant

    Hi Brian,

    Thanks for the reply. I just tried setting a recurring event’s timezone to UTC-0 and adjusting the time. The event occurs from 7:30AM to 8:00AM. I adjusted by subtracting 5 hours (we’re in EST) and saved the event (in UTC-0) with the custom rule set to 2:30AM to 3:00AM and it published with a length of 8.5 hours. Am I not adjusting for timezone appropriately? Thanks.

    #1024243
    Brian
    Member

    Hi,

    Leave your timezones to the location you are in. Those do not need to be changed.

    Only change the new time with the offset in the recurring event settings.

    Try that and see if it works better.

    #1024244
    William
    Participant

    That’s actually what (I think) I did. That is, I didn’t adjust the timezone setting under Dashboard > Settings (for the whole site), only within the specific Recurring Post’s ‘Edit Event’ page, and still got the undesired results.

    #1024250
    Brian
    Member

    Ok,

    Can you give me all the recurring settings you are using and your timezone and I will see if I can get it to work.

    Thanks

    #1024261
    William
    Participant

    Start Date & Time: 2015-11-16 6:00 AM
    End Date & Time: 2015-11-16 7:00 AM
    Timezone: UTC-0

    Recurrence Rules:

    1. Every Week and will end on 2015-11-30 (works)
    2. Custom and will end on 2015-12-07
    Sunday (Checked) From 2:30 AM to 3:00 AM (pre-save)
    8:30 AM to 5:00 PM (after save)

    This is what it looks like before I save. I’ll attach a link to a screenshot.

    Time Settings Screenshot

    #1024422
    Brian
    Member

    Hi,

    So I noticed you are using Pro 3.12, but we are up to 3.12.6 and there was a lot of changes made to fix issues with the Recurring Events so that might help.

    I was able to get the times right using your settings with UTC 0 as my timezone.

    However, it also created events on November 22 @ 2:30 am – 3:00 am and November 29 @ 2:30 am – 3:00 am so you might have to make exclusions for those two days…

    We are also having issues with exclusions so that might not work, but if they are created you could just come back and delete them and you would be set.

    Let me if that works after the upgrade.

    #1039257
    Geoff
    Member

    Hey there,

    Just jumping in to let you now that the patch for this issue is included in 4.0.1 and it just released today. Keep your eyes open for the update and please do let us know if any other issues pop up and we’d be happy to help. 🙂

    Cheers!
    Geoff

Viewing 9 posts - 1 through 9 (of 9 total)
  • The topic ‘Recurring Events Saving Wrong Custom Recurrance Time’ is closed to new replies.