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
When i submit a order a email is send to receiver. In Method is missing a try catch block and then when receiver-address is wrong or SMTP Server data is wrong payment is not successfull and message to customer is not good. Please make a try catch block to
venv/lib/python3.8/site-packages/oscar/apps/communication/utils.py Line 128
Steps to Reproduce
It's essential that you provide enough information for someone else to replicate the problem you're seeing. Simply describing something that's broken on your current project is not enough!
Insert in settings.py wrong SMTP data
Buy Product and on place order site place this order. Then browser loads approx. 1 Min and then you get error on backend and user get a misterious message
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
Python version: Run 3.8.
Django version: 3.2
Oscar version: Look in your requirements.txt, or run 3.1.
The text was updated successfully, but these errors were encountered:
We could add try-except block and log the exception rather than letting it raise.
However, most projects (I hope) override this method by implementing their chosen que/task system for mailing (such as celery, uwsgi-spooler, django-mailer etc), so I'm not sure if it really is a issue.
Found a bug? Please fill out the sections below.
Issue Summary
When i submit a order a email is send to receiver. In Method is missing a try catch block and then when receiver-address is wrong or SMTP Server data is wrong payment is not successfull and message to customer is not good. Please make a try catch block to
venv/lib/python3.8/site-packages/oscar/apps/communication/utils.py Line 128
Steps to Reproduce
It's essential that you provide enough information for someone else to replicate the problem you're seeing. Simply describing something that's broken on your current project is not enough!
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
3.8
.3.1
.The text was updated successfully, but these errors were encountered: