Rendering Placement Issue -Shopping Cart Items After Container in Widget

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

http://www.magento.com

Open Software License 3.0

11.56k stars 9.32k forks source link

Rendering Placement Issue -Shopping Cart Items After Container in Widget #27833

Closed ajithkumar-maragathavel closed 4 years ago

ajithkumar-maragathavel commented 4 years ago

Preconditions (*)

Goto Content -> Elements -> Blocks -> Click Add New Block , Create and save a new cms block with any content.
Goto Content -> Elements -> Widgets -> Click Add Widget, Create a widget with the following options and layout updates.

Type -> CMS Static Block Display on -> Specified Page Page -> Shopping Cart Container -> Shopping Cart Items After Block -> Select the cms block created in the above step.

Steps to reproduce (*)

Create a new CMS Block with any content.
Create a new Widget with the conditions specified in the preconditions.
Add any product to the cart and navigate to the shopping cart page.
Widget is rendered above the shopping cart items section.

Expected result (*)

Since I have selected Shopping Cart Items After in the widget configuration, the widget should be rendered below the shopping cart items section. ss2-expected

Actual result (*)

But the widget is rendered above the shopping cart items section. Please see the below attachment. ss-1-actual

m2-assistant[bot] commented 4 years ago

Hi @ajithkumar-maragathavel. Thank you for your report. To help us process this issue please make sure that you provided the following information:

[x] Summary of the issue
[x] Information on your environment
[x] Steps to reproduce
[x] 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.4-develop instance - upcoming 2.4.x release

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

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

[x] yes
[ ] no

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

ajithkumar-maragathavel commented 4 years ago

@magento give me 2.4-develop instance

magento-engcom-team commented 4 years ago

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

magento-engcom-team commented 4 years ago

Hi @ajithkumar-maragathavel, here is your Magento instance. Admin access: https://i-27833-2-4-develop.instances.magento-community.engineering/admin_77eb Login: 7f504185 Password: 8209a4625495 Instance will be terminated in up to 3 hours.

m2-assistant[bot] commented 4 years ago

Hi @ajithkumar-maragathavel. 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:

[x] 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.
[x] 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.
[x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[x] 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!

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

m2-assistant[bot] commented 4 years ago

Hi @krishprakash. 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:

[x] 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.
[x] 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.
[x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[x] 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!
[x] 5. Add label Issue: Confirmed once verification is complete.
[x] 6. Make sure that automatic system confirms that report has been added to the backlog.

krishprakash commented 4 years ago

@magento give me 2.4-develop instance

magento-engcom-team commented 4 years ago

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

magento-engcom-team commented 4 years ago

Hi @krishprakash, here is your Magento instance. Admin access: https://i-27833-2-4-develop.instances.magento-community.engineering/admin_a873 Login: d73d386b Password: 3496b05de060 Instance will be terminated in up to 3 hours.

magento-engcom-team commented 4 years ago

:white_check_mark: Confirmed by @krishprakash Thank you for verifying the issue. Based on the provided information internal tickets MC-33343 were created

Issue Available: @krishprakash, 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 commented 4 years ago

Hi @ajithkumar-maragathavel. Thank you for your report. The issue has been fixed in magento/magento2#27834 by @ajithkumar-maragathavel in 2.4-develop branch Related commit(s):

a11126d08eae713e49b547f3cd27aeaccf6c0b53

The fix will be available with the upcoming 2.4.0 release.

magento-engcom-team commented 3 years ago

Hi @ajithkumar-maragathavel, @ajithkumar-maragathavel.

Thank you for your report and collaboration!

The related internal Jira ticket MC-33343 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.