Describe the bug:
An e-mail to confirm a completed purchase is not being sent to the user's entered email inbox.
Expected behavior:
After a purchase, the user should be getting a purchase confirmation email, with all the details about the purchase but also the booking process of the dream experience they have bought.
Solution:
The 'solution' is to not make the user confused thinking they will receive an email, therefor the feature is better off to be removed for now. To make the user experience as good as possible, some of the information from the confirmation email is being displayed in the checkout success page instead, to let the user know the booking process. This can be seen as a screenshot under the list of features in the README.
The bug is probably related to the webhook handler and will be investigated and solved in the future. The related code in the webhook_handler.py was cut out together with the post purchase email templates and are saved and can be reviewed in my Gists
Solved:
Temporarily solved by removing the feature for now until it can be solved and implemented.
Describe the bug: An e-mail to confirm a completed purchase is not being sent to the user's entered email inbox.
Expected behavior: After a purchase, the user should be getting a purchase confirmation email, with all the details about the purchase but also the booking process of the dream experience they have bought.
Solution: The 'solution' is to not make the user confused thinking they will receive an email, therefor the feature is better off to be removed for now. To make the user experience as good as possible, some of the information from the confirmation email is being displayed in the checkout success page instead, to let the user know the booking process. This can be seen as a screenshot under the list of features in the README. The bug is probably related to the webhook handler and will be investigated and solved in the future. The related code in the webhook_handler.py was cut out together with the post purchase email templates and are saved and can be reviewed in my Gists
Solved: Temporarily solved by removing the feature for now until it can be solved and implemented.