-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magento 2.4.5-p1 Reorder issue #36739
Comments
Hi @niku0911. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @engcom-Bravo. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Bravo, here is your Magento Instance: https://c13daff8daa43ce9bc703e6cf12ae422.instances.magento-community.engineering |
Hi @niku0911, Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance and the issue is not reproducible. Kindly refer the screenhsots. Steps to reproduce 1.Create a simple product with a custom option We are able to reorder the same product without any error. Kindly recheck the behavior on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible. Thanks. |
@niku0911 what does the log say for the error? The log will be located as a file on the server here: /public_html/var/log/system.log For future reference, always post the log (just the error at the time though, no need to post the whole thing), it helps others help you. |
HI @FadedOut [2023-01-13T04:42:49.028492+00:00] main.CRITICAL: TypeError: Magento\Framework\DataObject::__construct(): Argument #1 ($data) must be of type array, null given, called in /home/awarenessplace/public_html/uat/vendor/magento/module-sales/Model/Reorder/OrderInfoBuyRequestGetter.php on line 65 and defined in /home/awarenessplace/public_html/uat/vendor/magento/framework/DataObject.php:39 |
@magento give me 2.4.5-p1 instance |
Hi @FadedOut. Thank you for your request. I'm working on Magento instance for you. |
Hi @FadedOut, here is your Magento Instance: https://6dfb7d1c90e1542c32219ccbf960c8a5.instances.magento-community.engineering |
@niku0911 Hmm so unfortunately, I may not be able to help - and I hate that :(. I wish I could have given you solution, I was hoping maybe it was because you had it set to 0 characters that maybe it was bugging out - but I copied your custom field exactly and it went through. I'll attach the screenshots and video of my test. And the log you posted I'm not sure why it would be throwing that. So you say that the order goes through the first time, but the custom field doesn't show on the order screen (as your screenshot shows)....that is odd, esp that there is no error on the frontend from the first time the order was placed and succeeded only during re-order. Is there any error in the log when you place the order (the first time - not the reorder)? I've had errors appear in the log but show no sign of an error on the UI side. magento-github-topic-reorder-test-video-1.mp4 |
Hi @FadedOut, so might be an issue with 3rd party extension, will check this on our side on this. |
Hi. We have almost the same problem, but the log is:
|
The thing is that in |
Reorder having an issue with Custom option Product
Preconditions (*)
Magento version: 2.4.5-p1
Steps to reproduce (*)
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: