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

Recurring Events - Miscalculated Time Blocks #233

Closed
TySol opened this issue Aug 9, 2016 · 3 comments
Closed

Recurring Events - Miscalculated Time Blocks #233

TySol opened this issue Aug 9, 2016 · 3 comments
Labels
Milestone

Comments

@TySol
Copy link

TySol commented Aug 9, 2016

  • Recurring events won't load into the time slots they are supposed to occupy
  • Often it skips time slots leaving holes in an event's time block, and usually doesn't begin on the intended start time.
  • Experienced when any rrules are being applied, i.e: Daily, Weekly, Monthly, Yearly
  • Bug displays in Calendar_day.html

Pictured example: This weekly-recurring event is supposed to start at 8:00 and go until 11:30, but instead starts at 11:00 and goes until 15:00, with holes at 12:00 and 13:30

scheduler recurring bug

I've been extending this app for a few months now to learn more about Django, and after making significant progress in other areas this issue still has me stumped. The last few days I've rolled back my schedule app to the clean Development branch to see if it was something I caused but I'm still experiencing the issue. Any information that can point me in the right direction to fix this is much appreciated!

@TySol
Copy link
Author

TySol commented Aug 10, 2016

I haven't yet pinpointed what is going wrong here, but the issue seems to be affecting the reccuring occurences as well:
#231: recurring events with multiple "byweekday"s return wrong occurences

And as mentioned in previous issues, I've tried inputting params to match the weekday, i.e: Weekly byweekday:2

#204: rule params

#229: document dateutil's rule's interval parameter

@llazzaro
Copy link
Owner

ok let me know if you find the issue. an unit test could be very helpful for this case.

In the past I was going to do a heavy refactor on the models since are very difficult to use.

@mpaolino
Copy link
Contributor

mpaolino commented Jan 4, 2017

This should be solved by #271

@llazzaro llazzaro closed this as completed Jan 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants