Skip to content

[CMS Product Block] Configurable Product Does Not Respect Sort Order When Its Child Simple Product Matches Condition #39929

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.

Sign up for GitHub

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

Jump to bottom
Open
1 of 5 tasks
ph4mHoa opened this issue May 22, 2025 · 6 comments · May be fixed by #39935
Open
1 of 5 tasks

[CMS Product Block] Configurable Product Does Not Respect Sort Order When Its Child Simple Product Matches Condition #39929

ph4mHoa opened this issue May 22, 2025 · 6 comments · May be fixed by #39935
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.8 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@ph4mHoa
Copy link

ph4mHoa commented May 22, 2025

Preconditions and environment

  • Magento version 2.4.7, 2.4.8
  • Block Product have condition that include a simple product

Steps to reproduce

  1. Set up a condition that includes a simple product.
    (In this example, I chose to create a new category that include a simple product.)

Image
2. Set up a cms page.
Setup Block Product 1 :
Image
Set up Block Product 2:
Image
3. Access the new page and observe

Expected result

Expected Result:
The products rendered by Block Product must follow the specified sorting conditions.

Actual result

Output:
Image
The configurable product that includes the simple product matching the condition does not follow the sorting order — it always appears first.

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented May 22, 2025

Hi @ph4mHoa. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board May 22, 2025
@engcom-Bravo engcom-Bravo self-assigned this May 22, 2025
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented May 22, 2025

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).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- 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.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.8 Indicates original Magento version for the Issue report. label May 22, 2025
@engcom-Bravo
Copy link
Contributor

Hi @ph4mHoa,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in latest 2.4-develop instance and we are able to reproduce the issue.Kindly refer the screenshots.

Image

The configurable product that includes the simple product matching the condition does not follow the sorting order — it always appears first.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: Catalog labels May 22, 2025
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14758 is successfully created for this GitHub issue.

@ct-prd-projects-boards-automation ct-prd-projects-boards-automation bot moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board May 22, 2025
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented May 22, 2025

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
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.

@ct-prd-projects-boards-automation ct-prd-projects-boards-automation bot moved this to Ready for Development in High Priority Backlog May 22, 2025
@ananth-iyer
Copy link
Member

@ph4mHoa I HAVE FOUND NO ISSUE.

I FOLLOW THIS STEPS - DRAG THE ICON SO IT WILL CHANGE POSITION OF THE SWATCHES ON PDP AND PLP PAGES.

After this save:

  1. run full reindex
  2. Clean full cache

It requires extra steps to apply the changes on frontend.

Image

ph4mHoa added a commit to ph4mHoa/magento2 that referenced this issue May 23, 2025
@ph4mHoa
fix-configurable-sorting-child-match-39929
7d22d04 
magento#39929
@ph4mHoa ph4mHoa mentioned this issue May 23, 2025
Closed
5 tasks
ph4mHoa added a commit to ph4mHoa/magento2 that referenced this issue May 23, 2025
@ph4mHoa
fix-configurable-sorting-child-match-39929
3a7e3c6 
magento#39929
@ph4mHoa ph4mHoa linked a pull request May 23, 2025 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.8 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
High Priority Backlog
Status: Ready for Development
Milestone
No milestone
4 participants
@ananth-iyer @ph4mHoa @engcom-Bravo @github-jira-sync-bot