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

Signals - Feature request #23

Closed
zen4ever opened this issue Sep 22, 2009 · 2 comments
Closed

Signals - Feature request #23

zen4ever opened this issue Sep 22, 2009 · 2 comments

Comments

@zen4ever
Copy link

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.

@bartekgorny
Copy link
Collaborator

Please do so, I think it is a good idea.

@zen4ever
Copy link
Author

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
Converted django-scheduler to use static files
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants