Magento/Multishipping: Setting wrong back url on creation New Customer Shipping Address Page

[Totem4ik]

Preconditions (*)

1. Magento 2.3.2
2. Sample data installed

Steps to reproduce (*)

1. Create new customer (customer should not have addresses).
2. Add some product to cart.
3. Open cart.
4. Click "Check Out with Multiple Addresses".
5. On "Create shipping address" page click "Back button".

Expected result (*)

1. Url in Back button : https://example.com/checkout/cart/.
2. Back on checkout cart.

Actual result (*)

1. Url in Back button : https://example.com/multishipping/cart/.
2. Get 404 page.

[m2-assistant]

Hi @Totem4ik. 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 give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Bravo. 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. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant]

Hi @ajijshekh123. 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. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[ajijshekh123]

Give me @magento give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[ajijshekh123]

@Totem4ik - I have reproduced this issue as per your steps and scenario. Back functionality is working fine in the latest Magento 2.3 instance.
Please review attach the video:

[Totem4ik]

@ajijshekh123 Hi! Thank you! One more detail what i missed. "Back Button" hide on this theme, but if you make a visible this block, you'll see that problem.
I attach two images to show you what i mean

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-20370 were created

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

[MaxSouza]

@Totem4ik for default the button is hidden, so it does not an error. We can't reproduced your issue.

[Totem4ik]

@MaxSouza you have this functionality in core of magento2 on backend. So, behavior of this functional is wrong. This doesn't a theme problem, this problem in core, so when we using another theme this bug doesn't hidden. How to reproduce this issue you can find above in topic and comment with screenshot.
Could you remove behavior of this button from controller or fix it ?

[m2-assistant]

Hi @MaxSouza. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[MaxSouza]

@Totem4ik Ah ok, I'll fix the url.

[magento-engcom-team]

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

• 7c5e7178abdb799062b67230589e4b7c70f8213c
• a528841c676f188824ca30479ca3e1d801b729c4
• 88532ef5e2cd5b580250793c39f7b1ae32e93815
• ecb2249fd67ce4d489e81c131349191c7256268b
• fded460ee1bc92156ff479e29115fe06fbbaffaa

The fix will be available with the upcoming 2.3.4 release.