What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi all, Does anyone know when the confirmation email is sent after an order is placed and what class
Hi all,
Does anyone know when the confirmation email is sent after an order is placed and what class sends it ?
I'm placing debuging breakpoints in the mailer Class but the code never flows through it.
Comments
-
This is done asynchronously from the OMS state-machine. You need to debug the command
console oms:check-condition
, I believe0 -
Thanks! I'll give it a shot.
0 -
Also if you run the containers in debug mode with
docker/sdk up -x
you can use breakpoints with background processes as well0 -
@U01T075RRHD I got my hands on the code since yesterday, but fail to understand the purpose of the command you sent.
If I understand correctly though, the confirmation email is not sent right after the checkout success, but rather via another module when the order is effectively placed, correct ?@U04BT4XGQF8 I've just recently started using xdebug, and am loving it ! I'm using break points but if I don't know where in the code the email is sent, how do I know where to put a break point? Furthermore, what are the "background processes" you mentionned ?
0 -
You'll find the OMS flow defined in an .xml file in the config/Zed/oms folder. Under , there are items like:
<event name="confirm" onEnter="true" manual="true" command="Oms/SendOrderConfirmation"/>
The command part is defined in OmsDependencyProvider::extendCommandPlugins where you'll also see what actual class it uses, which in this case is \Spryker\Zed\Oms\Communication\Plugin\Oms\Command\SendOrderConfirmationPlugin. This is one place you can put a breakpoint (the class file)
0 -
-
Try looking for
Oms/SendOrderConfirmation
in the code base. You will find a mapping to a class that you can start debugging0 -
And by background process in this case I mean, that if and when there are parts of the OMS flow that are not run back-to-back ( has onEnter="true") but rather scheduled ( has timeout=something), your xdebug breakpoint won't trigger since that request isn't (necessarily - there are of course exceptions...) sent from your browser
0 -
Thanks for your help !
I understand the process better now and managed to implement the changes I needed π0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 74 Spryker News
- 912 Developer Corner
- 772 Spryker Development
- 87 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 69 Spryker Safari Questions
- 50 Random