Magento2: Payment Method Not Showing Admin Sales Grid only check method showing.

[pushpendra07]

Payment Method showing blank always except check method

Preconditions (*)

1. Magento version 2.3.1

Steps to reproduce (*)

1. Create a simple order with bank transfer or COD.
2. Check Admin Sales order grid

Expected result (*)

1. Show Payment method in grid

Actual result (*)

1.Only Check method showing in the list

1. Order Edit window showing payment details

[m2-assistant[bot]]

Hi @pushpendra07. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@pushpendra07 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

[m2-assistant[bot]]

Hi @krishprakash. 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:

• [x] 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.

• [x] 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.

• [x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [x] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

[krishprakash]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22231-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[krishprakash]

[krishprakash]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22231-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[krishprakash]

[m2-assistant[bot]]

Hi @shikhamis11. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

:white_check_mark: Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99111, MAGETWO-99112 were created

Issue Available: @shikhamis11, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[amelojunior]

temporary fix...

add to etc/config.xml:

<default>
    <payment>
        <cashondelivery>
            <active>1</active>
        </cashondelivery>
        <banktransfer>
            <active>1</active>
        </banktransfer>
    </payment>
</default>

[domeglic]

The problem seems to be a new condition that checks for active payments, but somehow it returns wrong results because in my case the missing methods are active.

[Julen10]

@domeglic So, what´s a possible solution for this one?

[domeglic]

@Julen10 No idea what a proper solution is, I didn't look into why this additional check was added. The way I solved this for my project is to revert the change only for the sales grid:

Create a class that extends Magento/Payment/Helper/Data and removes the active check. Then set it as the argument for the column renderer:

<type name="Magento\Payment\Ui\Component\Listing\Column\Method\Options">
        <arguments>
            <argument name="paymentHelper" xsi:type="object">Vendor\Module\Bugfix\Payment\HelperData</argument>
        </arguments>
    </type>

[magento-engcom-team]

Hi @pushpendra07, @Nazar65, @krishprakash.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.2-develop branch(es).
Related commit(s):

• 08ecfe1efad526cb83fe0495e6e6f1459516b760
• 08daad82fdfde389be7695dcab5765de4f5326a1

The fix will be available with the upcoming 2.2.10 release.

[magento-engcom-team]

Hi @pushpendra07, @Nazar65, @krishprakash.

Thank you for your report and collaboration!

The issue was fixed by Magento team. The fix was delivered into magento/magento2:2.3-develop branch(es).
Related commit(s):

• da0c7374e5dcae81735552bdd685ee5e646b8486
• 4344cc9bc34fbda80dc798ebafcf80c516788442

The fix will be available with the upcoming 2.3.3 release.