6

I have upgraded from Magento EE 2.2.10 to 2.3.4, I had some content blocks with custom html used for navigation links on various pages that were just tags. After upgrading If I try to edit a content block It is now wrapped in the html below. This extra html breaks the CSS and JavaScript I had for the nav links. Is there a way to remove this html wrapper?

<div data-content-type="row" data-appearance="contained" data-element="main">
 <div data-enable-parallax="0" data-parallax-speed="0.5" data-background-images="{}" data-element="inner" style="justify-content: flex-start; display: flex; flex-direction: column; background-position: left top; background-size: cover; background-repeat: no-repeat; background-attachment: scroll; border-style: none; border-width: 1px; border-radius: 0px; margin: 0px 0px 10px; padding: 10px;">
 <div data-content-type="html" data-appearance="default" data-element="main" style="border-style: none; border-width: 1px; border-radius: 0px; margin: 0px; padding: 0px;" data-decoded="true">
 </div>
 </div>
</div>
asked Feb 3, 2020 at 21:58
7
  • Why did this get edited to have Magento 2.2.3 in the title? Commented Feb 4, 2020 at 18:32
  • good question, I would have tagged it with 2.3.4 but that tag was not available to use Commented Feb 5, 2020 at 17:15
  • This affects 2.3.2-p2 as well Commented Feb 7, 2020 at 8:52
  • According to magento support this is what is supposed to be output and they did not give any way around it. Commented Feb 7, 2020 at 13:53
  • Me also facing this issue, any workarounds? Commented Feb 21, 2020 at 10:13

1 Answer 1

4

I finally figured this out. Each row that has it's own properties which by default is set to to 'Contained' which is 1170px with 10px padding and 10px bottom margin. This is automatically added to a block if you edit it the first time. You can hover over row and then there will be a toolbar for the row. Click the properties icon, select 'Full Bleed' and go down to the bottom and set the padding to 0px and bottom margin to 0px. You mean need to re-index and/or clear cache. Then it should be good, at last this fixed it for me

answered Feb 24, 2020 at 19:41

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.