1đź‘Ť
Create your own custom signal and send it at the point when you have the data you need saved. Pass in as parameters whatever data structures you need.
Listen for your custom signal in your callback function email_order_on_save
and make appropriate decisions based on the parameters about sending or not the e-mail.
3đź‘Ť
I’m guessing you’re trying to solve this in the wrong place. Sending an email when the order is completed and saving the Order model are at different levels of abstraction.
I think sending the email should be triggered by some condition in the view that has more information about whether the order is completely saved or not. Think for example of what will happen if an order needs updating (say it’s status changes)? Should the email be sent then too?
- [Django]-Calling a Django view using Dajax
- [Django]-Your PYTHONPATH points to a site-packages dir for Python 3.x but you are running Python 2.x
1đź‘Ť
You could create your model as follows
ORDER_STATE = (
(1, 'Completed'),
(2, 'Processing'),
)
class Order(models.Model):
user = models.ForeignKey(User)
state = models.IntegerField(choices = ORDER_STATE)
You could have many states for the order. The state “Completed” could represent that the order processing is complete. You could change the state of your order in your views.
In the signal handler, you could check for the state of the order and then send mail, if the order is in completed state.
0đź‘Ť
I think you can have a problem with signals, OrderItem with inlines will not send save signal, read this
- [Django]-How to run python script inside django project?
- [Django]-Specifying Django Query Filters at Run Time