python
Recurring entries from the user group calendar are not shown
See https://www.python.org/events/python-user-group/ and compare to http://www.pycon.org/#calendar
Most entries in the user group calendar are recurring entries, so the website is missing out on most such events. It only shows events which are not recurring.
It would be great if we could finally fix this, since it's a known issue which has been open for 1.5 years now (see #335).
@malemburg I agree. The recurring events should be included.
I wonder if this is a bug with the rule mixins within the event model and how next_event is handled.
The bug still persists. This event is setup as a recurring event, but not shown on the website:
https://calendar.google.com/calendar/event?eid=XzZncTM4bzloYzhyNjZiYjM2a3IzYWI5a2M4cm02YmIxNzFoamdiOW1jb3FqaWRoaGNncWo2cGI2NjRfMjAyMTA5MTRUMDMzMDAwWiAzaGFpZzJtOW1zc2xrcGYydG4xaDU2bm45Z0Bn&ctz=Etc/GMT
The same goes for all other recurring user group event (of which we have many).
Would be great if we could get this fixed :-)
I assigned the bug to @berkerpeksag and @ewdurbin in the hope that we get some movement on this rather serious bug. It's been open since 2014. Feel free to assign it to others.
Since most user group events are recurring events, the website is missing out on a lot of fun:
whereas the website shows this for today:
hi i do not know what you say .what is meaning every week my event listed with recurring? good luck god willing
I've had a look at a few python.org database entries and they all seem to have only an "Occuring rule" entry instead of a "Recurring rule" entry. I've now deleted the entry for "PyDelhi User Group Meetup" from the database to see whether the entry gets picked up with correct "Recurring rule" in the next cronjob run.
Hmm, looking at the code in https://github.com/python/pythondotorg/blob/main/events/importer.py there doesn't seem to be any support for importing recurring events from the Google calendars. This would explain why they don't work :facepalm:
I've had a look at a few python.org database entries and they all seem to have only an "Occurring rule" entry instead of a "Recurring rule" entry. I've now deleted the entry for "PyDelhi User Group Meetup" from the database to see whether the entry gets picked up with correct "Recurring rule" in the next cronjob run.
The system recreated the entry, but only with an "Occurring rule" pointing to the first instance of the event. After looking at the code, this is not surprising.
I guess we'll have to mark this as feature request.
he recurring events should be included.
I wonder if this is a bug with the rule mixins within the event model and how next_event is handled.
