Order placed event
I use sales_order_save_commit_after
for same change to shipment and after this i save new subtotal and grand total, it's worked very well for COD but when i wanna use to another online payment the grand total that send to bank is last amount.
For example if the last amount is 500$
and new amount after my change is 800$
, 500$
sent to bank.
After many debug i found sales_order_save_commit_after
observer run after payment.
My question is : which order place event was fire before payment and is more like sales_order_save_commit_after
event ?
magento2 orders event-observer payment-methods
add a comment |
I use sales_order_save_commit_after
for same change to shipment and after this i save new subtotal and grand total, it's worked very well for COD but when i wanna use to another online payment the grand total that send to bank is last amount.
For example if the last amount is 500$
and new amount after my change is 800$
, 500$
sent to bank.
After many debug i found sales_order_save_commit_after
observer run after payment.
My question is : which order place event was fire before payment and is more like sales_order_save_commit_after
event ?
magento2 orders event-observer payment-methods
add a comment |
I use sales_order_save_commit_after
for same change to shipment and after this i save new subtotal and grand total, it's worked very well for COD but when i wanna use to another online payment the grand total that send to bank is last amount.
For example if the last amount is 500$
and new amount after my change is 800$
, 500$
sent to bank.
After many debug i found sales_order_save_commit_after
observer run after payment.
My question is : which order place event was fire before payment and is more like sales_order_save_commit_after
event ?
magento2 orders event-observer payment-methods
I use sales_order_save_commit_after
for same change to shipment and after this i save new subtotal and grand total, it's worked very well for COD but when i wanna use to another online payment the grand total that send to bank is last amount.
For example if the last amount is 500$
and new amount after my change is 800$
, 500$
sent to bank.
After many debug i found sales_order_save_commit_after
observer run after payment.
My question is : which order place event was fire before payment and is more like sales_order_save_commit_after
event ?
magento2 orders event-observer payment-methods
magento2 orders event-observer payment-methods
edited yesterday
PЯINCƏ
7,74121136
7,74121136
asked yesterday
gh darvishanigh darvishani
286215
286215
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
sales_order_save_commit_after
runs after the order has been fully processed and saved to the database. If you are altering the order data, you want to do that before data has been saved. Moreover, if you are altering amounts, you want to do it before placement has occurred. Placement ($order->place()
) is when payment is processed.
Try this event: sales_order_place_before
You can find it in MagentoSalesModelOrder
.
If that won't work for your case, you'll need to give more details as to why.
add a comment |
for each action's controller Magento 2 have one event . i use payment action for fixed my bug and it worked very well .
Of course i know it is not good solution but it fixed my problem.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256873%2forder-placed-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
sales_order_save_commit_after
runs after the order has been fully processed and saved to the database. If you are altering the order data, you want to do that before data has been saved. Moreover, if you are altering amounts, you want to do it before placement has occurred. Placement ($order->place()
) is when payment is processed.
Try this event: sales_order_place_before
You can find it in MagentoSalesModelOrder
.
If that won't work for your case, you'll need to give more details as to why.
add a comment |
sales_order_save_commit_after
runs after the order has been fully processed and saved to the database. If you are altering the order data, you want to do that before data has been saved. Moreover, if you are altering amounts, you want to do it before placement has occurred. Placement ($order->place()
) is when payment is processed.
Try this event: sales_order_place_before
You can find it in MagentoSalesModelOrder
.
If that won't work for your case, you'll need to give more details as to why.
add a comment |
sales_order_save_commit_after
runs after the order has been fully processed and saved to the database. If you are altering the order data, you want to do that before data has been saved. Moreover, if you are altering amounts, you want to do it before placement has occurred. Placement ($order->place()
) is when payment is processed.
Try this event: sales_order_place_before
You can find it in MagentoSalesModelOrder
.
If that won't work for your case, you'll need to give more details as to why.
sales_order_save_commit_after
runs after the order has been fully processed and saved to the database. If you are altering the order data, you want to do that before data has been saved. Moreover, if you are altering amounts, you want to do it before placement has occurred. Placement ($order->place()
) is when payment is processed.
Try this event: sales_order_place_before
You can find it in MagentoSalesModelOrder
.
If that won't work for your case, you'll need to give more details as to why.
answered yesterday
Ryan HoerrRyan Hoerr
8,37433042
8,37433042
add a comment |
add a comment |
for each action's controller Magento 2 have one event . i use payment action for fixed my bug and it worked very well .
Of course i know it is not good solution but it fixed my problem.
add a comment |
for each action's controller Magento 2 have one event . i use payment action for fixed my bug and it worked very well .
Of course i know it is not good solution but it fixed my problem.
add a comment |
for each action's controller Magento 2 have one event . i use payment action for fixed my bug and it worked very well .
Of course i know it is not good solution but it fixed my problem.
for each action's controller Magento 2 have one event . i use payment action for fixed my bug and it worked very well .
Of course i know it is not good solution but it fixed my problem.
answered 4 hours ago
gh darvishanigh darvishani
286215
286215
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256873%2forder-placed-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown