"- undefined" displayed in checkout summary when shipping method name is not set

[krzksz]

Sometimes it is the case that setting both Carrier title and Method name for a shipping method is redundant and having only the first one set it totally enough. Sadly, in the case of leaving Method name field blank there is a small visual bug displayed in checkout summary box.

Preconditions

1. Magento 2.2.x, but any version may be affected
2. Shipping method with empty Method Name set.

Steps to reproduce

1. Add new or edit any existing shipping methods with Method name field left as a blank field.
2. Add any product to the cart and go through the checkout to the last step.

Expected result

1. Shipping method is displayed nicely.

Actual result

1. There is a - undefined string displayed.

[magento-engcom-team]

Hi @krzksz. 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 {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[krzksz]

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

[magento-engcom-team]

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

[magento-engcom-team]

Hi @krzksz, here is your Magento instance.
Admin access: https://i-17492-2-2-develop.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ghost]

@krzksz , thank you for your report.
We've acknowledged the issue and added to our backlog.

[magento-engcom-team]

Hi @krzksz. Thank you for your report.
The issue has been fixed in #17526 by @gelanivishal in 2.2-develop branch
Related commit(s):

• c789fb2813a74d5333fbcddca7f92b0a0c245162
• 7aecb1f3c73e9af00375deabdfdc2bc78186e735

The fix will be available with the upcoming 2.2.7 release.

[magento-engcom-team]

Hi @krzksz. Thank you for your report.
The issue has been fixed in #17697 by @gelanivishal in 2.3-develop branch
Related commit(s):

• 667e276ffcb41927bb07648f5e0e01ad8a733e5e
• d85dd69d40acdcc4934a9f0f2fc3ebbbb9f8eb40
• cd7c2b197cfb9db5e7aa1de10dfa95528bd57ad3

The fix will be available with the upcoming 2.3.0 release.

[orlangur]

This seems to be not fixed completely according to new linked PR.

[m2-assistant]

Hi @engcom-Alfa. 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: 👇

• 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 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 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]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-17845, MC-17846 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @krzksz.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.2.10 release.

[magento-engcom-team]

Hi @krzksz.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.3.3 release.