Closed victortodoran closed 2 days ago
Hi @victortodoran. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Verified the issue on Magento 2.4-develop branch and the issue is reproducible: Steps performed: Installed Brain-tree module on 2.4-develop branch Admin -> Stores -> Configuration -> Sales -> Payment methods -> Configure Brain-tree payment. Note: Set Debug mode to Yes Front-end -> Add a product to cart -> Checkout -> Make Brain-tree Payment - No Issue. User is able to place Order Now disable Brain-tree payment option from Admin (Remove brain-tree configuration from Admin - Stores - Configuration - Sales - Payment Methods) Cache flush and clear cache Navigate to Front-end - Add a product to Cart - Checkout - Make Payment using PayPal Express Checkout - User is able to place Order. Issue: MagentoRoot Folder/var/log/system.log -> Below Error message is gettting printed in system.log after placing orders using other payment modes : main.ERROR: Braintree\Configuration::merchantId needs to be set (or accessToken needs to be passed to Braintree\Gateway). [] []
:white_check_mark: Confirmed by @engcom-November
Thank you for verifying the issue. Based on the provided information internal tickets MC-42923
were created
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Hi @victortodoran ,
Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop and the issue is not reproducible. Kindly refer the screenshots.
Steps to reproduce -
Kindly recheck the issue on latest Magento 2.4-develop instance and Please let us know if you are still facing any issue. Thanks.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
MagentoRoot Folder/var/log/system.log -> Below Error message is gettting printed in system.log after placing orders using other payment modes : main.ERROR: Braintree\Configuration::merchantId needs to be set (or accessToken needs to be passed to Braintree\Gateway)
Please check this comment for more details about the configuration.
Additional info (*)
I don't want to disable the modules, the merchant might want to configure and use Braintree in the future and should not need me to re-enable the modules to do so. The cart and checkout pages try to load the config for a disabled payment method, it makes little sense, if it's disabled I certainly don't have a token configured for it.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.