Skip to content
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.

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

Fixes incorrectly nested html in the product items list template. #27926

Merged
merged 1 commit into from
Apr 25, 2020

Conversation

hostep
Copy link
Contributor

@hostep hostep commented Apr 21, 2020

Description (*)

MC-30989 introduced an incorrectly nested html structure in both Magento 2.3.5 and 2.4-develop

See #27920 for more details.

Fixed Issues (if relevant)

  1. [2.3.5] Incorrect html structure after MC-30989 #27920: [2.3.5] Incorrect html structure after MC-30989

Manual testing scenarios (*)

  1. Setup a clean Magento 2.3.5 or 2.4-develop (I've used commit 1e28f35)
  2. Create a couple of simple products in the backend of Magento which are saleable
  3. Open the first product you created and link the other products as crosssells to it
  4. Reindex & flush caches
  5. In the frontend, put that first product in your cart and go the the cart page
  6. Look at the layout of the crosssells, it looks correct:

crosssells-correct

  1. Simulate that the products are not saleable by changing the method Magento\Catalog\Model\Product::isSaleable to always return false
  2. Refresh the cart page, see that the layout of the crosssell products is completely broken

crosssells-incorrect

9. After applying this fix the layout will not look broken again

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Apr 21, 2020

Hi @hostep. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

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

Copy link
Contributor

@rogyar rogyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

@rogyar
Copy link
Contributor

rogyar commented Apr 22, 2020

The failing tests are not related to the current change

@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-7464 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Before: ✖️ layout of the crosssells is broken
before_last

After: ✔️ Now it looks correct
after_last

@magento-engcom-team
Copy link
Contributor

Hi @ptylek, thank you for the review.
ENGCOM-7464 has been created to process this Pull Request

@slavvka slavvka added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Apr 23, 2020
@slavvka slavvka added this to the 2.4.0 milestone Apr 23, 2020
@magento-engcom-team magento-engcom-team merged commit b1161c3 into magento:2.4-develop Apr 25, 2020
@m2-assistant
Copy link

m2-assistant bot commented Apr 25, 2020

Hi @hostep, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@hostep
Copy link
Contributor Author

hostep commented Apr 27, 2020

Thanks!

@slavvka: can we try to get this fix included in Magento 2.3.6 as well? Since the bug was introduced in 2.3.5.

@slavvka
Copy link
Member

slavvka commented Apr 28, 2020

@hostep I raised this question to our POs

@slavvka
Copy link
Member

slavvka commented Apr 28, 2020

Yes, they are going try to backport it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Award: bug fix Component: Catalog Priority: P3 May be fixed according to the position in the backlog. Progress: accept Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants