You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to add signals on event creation, and in some other major points
I've added signals for event creation/update in my fork. But I feel that it should be done in some systematic manner. I can devote some time to go though django-schedule so it will send signals in other major points (event deletion, occurrences crate/update/delete, etc).
In my case I needed to catch event_created to re-post created event into other calendars, and couldn't find the way to do it without rewriting the whole 'create_or_edit_event' view.
The text was updated successfully, but these errors were encountered:
Well, now that I'm rethinking it, it looks like there is not much sense to add custom signals for saving models, because I can use built-in Django pre_save/post_save, with 'created' argument for this purpose. I actually rewrote the code for the project I was working on to use post_save signal on Event model. Maybe I will come up with more ideas on using signals for some specific events inside of django-schedule later.
boardman
pushed a commit
to boardman/django-schedule
that referenced
this issue
Nov 26, 2013
It would be nice to add signals on event creation, and in some other major points
I've added signals for event creation/update in my fork. But I feel that it should be done in some systematic manner. I can devote some time to go though django-schedule so it will send signals in other major points (event deletion, occurrences crate/update/delete, etc).
In my case I needed to catch event_created to re-post created event into other calendars, and couldn't find the way to do it without rewriting the whole 'create_or_edit_event' view.
The text was updated successfully, but these errors were encountered: