Magento2: Insignificant stores sorting issue

[magecodenet]

Preconditions

1. Magento 2.1.2 Release Archive
2. Magento 2.4-develop

Steps to reproduce

1. Login to Admin
2. go to Stores -> All Stores.
3. Sort by any column

Expected result

Sorting should work or disable the sorting option

Actual result

sorting doesn't work

[VasylShvorak]

Thanks for reporting this issue. Created internal issue MAGETWO-69970 to investigate and track this issue.

[magento-engcom-team]

@magecodenet, thank you for your report.
We've created internal ticket(s) MAGETWO-69970 to track progress on the issue.

[afirlejczyk]

Hello @magento-engcom-team

I have an idea how to fix, but this view is using deprecated block

Magento\Backend\Block\Widget\Grid

I would like to fix this issue, but I am wondering - should I rebuild this view and use UI component to render store listing ?

[ishakhsuvarov]

Hi @afirlejczyk
Yes, you may do both ways, however migrating to use UI component is definitely a better approach.

[ishakhsuvarov]

Hi @afirlejczyk
Are you still interested in working on this?

[afirlejczyk]

Hi @ishakhsuvarov
Yes, I am. I will make a pull request within two weeks.

[magento-engcom-team]

Hi @magecodenet. Thank you for your report.
The issue has been fixed in magento/magento2#17371 by @afirlejczyk in 2.2-develop branch
Related commit(s):

• f16859318ee6f57f629b78a99717ad732e41c675
• 81fc5aa1135e094fb6a3c8f762e8123918c635e6
• c4fbe49677aac50c3fabffc7d8e67e060bccf581
• 8910b68ccf8b33863ff23da35ef941d9eeb153fd
• 7bc52b96586af3edc74174a477fe0689ee366ab1
• c0e78e0645382bee9e7739966ccb4c5dfd05f67b
• 471de671f98b8094e5e8fafc5bfaacfa8b213c46
• c60df27b883fcb082b8bb9239532667ad635a583
• 448a333e3bcd31c392625dabdf060a5363f383cc
• e6b17ad869da220c265b2ae2e227c67e85d1d193

The fix will be available with the upcoming 2.2.9 release.

[Vigneshmuthusamy]

The issue still persists in Magento version 2.3.4.

[Vigneshmuthusamy]

Ideally, we could remove the sorting option here. There won't be a scenario for a user to sort here. They will search if they want to which is already there.

[srsathish92]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @srsathish92, here is your Magento instance.
Admin access: https://i-7283-2-4-develop.instances.magento-community.engineering/admin_4c42
Login: b77b42f3 Password: 4b89a2fedd9b
Instance will be terminated in up to 3 hours.

[srsathish92]

@magento-engcom-team I can able to reproduce in given instance.

here is the proof:

====================================

[ghost]

:white_check_mark: Confirmed by @srsathish92
Thank you for verifying the issue! :+1: Your confirmation will help us to acknowledge and process this report.

[magento-engcom-team]

@srsathish92 Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [x] Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess
• [x] Update issue content to follow format required by Issue Reporting Guidelines

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[m2-assistant[bot]]

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: :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 branch

  Details

  - 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.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-31309 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._

[m2-assistant[bot]]

Hi @srsathish92. 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.4-develop branch

  Details

  - 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_!

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

[m2-assistant[bot]]

Hi @VinothKumar361. 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.4-develop branch

  Details

  - 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_!

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

[afirlejczyk]

Is anybody is working to port changes for Magento 2.3.4? If not I will try to port changes from Magento 2.2 https://github.com/magento/magento2/pull/17371

[m2-assistant[bot]]

Hi @nitish-ranjan05. 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.4-develop branch

  Details

  - 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_!

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

[nitish-ranjan05]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @nitish-ranjan05. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @nitish-ranjan05, here is your Magento instance.
Admin access: https://i-7283-2-4-develop.instances.magento-community.engineering/admin_0ae7
Login: 9734a2b3 Password: cbc5bcb13da2
Instance will be terminated in up to 3 hours.

[Bartlomiejsz]

@nitish-ranjan05 are you working on porting https://github.com/magento/magento2/pull/17371 to 2.4-develop? I started to migrate Stores listing to ui components when I wasn't aware that this was done in 2.2, so I could pick this up in case it would be free

[nitish-ranjan05]

@Bartlomiejsz @afirlejczyk It is available for work. you could pick it.

[m2-assistant[bot]]

Hi @Bartlomiejsz. 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.4-develop branch

  Details

  - 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_!

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

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Thank you for your contributions.