Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daylight savings and leap years not accounted for in engagement delay #2799

Open
4 tasks
brianhogg opened this issue Nov 11, 2024 · 0 comments
Open
4 tasks
Assignees

Comments

@brianhogg
Copy link
Contributor

Reproduction Steps

  1. Create an engagement with a multiple day delay
  2. Fulfill that engagement (ie. completing a course) before a daylight savings change or leap year day, such that today + the delay will be after the time change or skipped day
  3. Check when the engagement is scheduled under LifterLMS > Status > Scheduled Actions

Expected Behavior

The engagement happens when expected.

Actual Behavior

The engagement is an hour before or after the time expected (daylight savings change), or a day off (leap year)

This issue has be recreated:

  • Locally
  • On a staging site
  • On a production website
  • With only LifterLMS and a default theme
@ideadude ideadude moved this to Awaiting Triage in Development Nov 11, 2024
@ideadude ideadude self-assigned this Nov 11, 2024
@brianhogg brianhogg assigned brianhogg and unassigned ideadude Nov 11, 2024
@brianhogg brianhogg moved this from Awaiting Triage to Awaiting Review in Development Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Awaiting Review
Development

No branches or pull requests

2 participants