Skip to content
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

Correct location of transparent.js #19764

Merged

Conversation

pmclain
Copy link
Contributor

@pmclain pmclain commented Dec 14, 2018

Description (*)

The reference to this file was originally changed:
0ce439b#diff-7fec090bf536a50e1bdfa20e039e27edR9
0ce439b#diff-6de82c32cd46b3be45d4d65e403f4136R9

And the file was moved here:
0ce439b#diff-b0845d35ccdd892fe5e1a93a9b714b66

The file move was not ported to 2.3 but the requirejs-config was, breaking
admin sales order create with PayflowPro and Authorize.net

Fixed Issues (if relevant)

  1. Admin Sales Order Create Fails with PayflowPro #19763

Manual testing scenarios (*)

  1. Configure credit card payments for Payflow Pro
  2. Create order in admin panel
  3. adminhtml/Magento/backend/{{locale}}/Magento_Payment/js/transparent.js should not return a 404 error.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

The reference to this file was originally changed:
magento@0ce439b#diff-7fec090bf536a50e1bdfa20e039e27edR9
magento@0ce439b#diff-6de82c32cd46b3be45d4d65e403f4136R9

And the file was moved here:
magento@0ce439b#diff-b0845d35ccdd892fe5e1a93a9b714b66

The file move was not ported to 2.3 but the requirejs-config was, breaking
admin sales order create with PayflowPro and Authorize.net

Fixes magento#19763
@magento-engcom-team
Copy link
Contributor

Hi @pmclain. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@rogyar rogyar self-assigned this Dec 14, 2018
@magento-engcom-team magento-engcom-team added this to the Release: 2.3.1 milestone Dec 14, 2018
pmclain added a commit to pmclain/magento2 that referenced this pull request Dec 14, 2018
This sets the token `isVisible` value to faluse if
`VaultConfigProvider::IS_ACTIVE_CODE` is not set in the payment's
`additionalInformation` property. The value is not set when placing orders
through the admin panel, unless the save for later checkbox is selected. This
caused all admin order payment to be visible in the stored payment method
section in the storefront.

Fixes magento#19515

Testing on 2.3 depends on magento#19764
@VladimirZaets VladimirZaets self-assigned this Dec 14, 2018
@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-3690 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

Hi @pmclain. Thank you for your contribution.
We will aim to release these changes as part of 2.3.1.
Please check the release notes for final confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants