- π³π¬Nigeria chike Nigeria
Using Drupal 10.5.1 and Barrio 5.5.20 and having a slick image slider on the page, #8 fixed this issue.
Thanks.
- π³π¬Nigeria chike Nigeria
I didn't really have this issue as I thought. What I thought was a fix by #8 was because I was viewing the page as admin. After a few days I viewed as anonymous and the issue was there. It took me days of headaches and bewilderment to find that I had added this in a node template override,
{% if 'administrator' in user.getroles or 'manager' in user.getroles %} / <div class="property-views" title="Views"><i class="fas fa-eye" title="Page views"></i> {{ property_listing_views }}{% endif %}</div>
I neglected to format the code properly and also couldn't tell the closing
div
tag was outside theif
condition block. So this closingdiv
wasn't opened for anonymous users and it abruptly closed<div class="row row-offcanvas row-offcanvas-left clearfix">
tag leaving the sidebar outside of the grid. So for admins the page displayed properly and for anonymous the page broke.After days of trauma, I was able to track this down and the issue was gone. So sorry, this issue is no more existent, at least in my own experience.
- π³π¬Nigeria chike Nigeria
I discovered that even though my trailing
</div>
tag messed up the grid and the code at #8 was not working for anonymous users, that being my own error. Today I took off #8 from the live site and the issue came back! I looked at the markup and found,<div class="row row-offcanvas row-offcanvas-left clearfix flex"> <main class="main-content col" id="content" role="main"></main> <div class="sidebar_second sidebar col-md-3 order-last" id="sidebar_second"></div> ::after </div>
I put back #8 and the issue solved again. I looked at the markup again and found,
<div class="row row-offcanvas row-offcanvas-left clearfix flex"> <main class="main-content col col-md-9" id="content" role="main"> <section class="section"></section> </main> <div class="sidebar_second sidebar col-md-3 order-last" id="sidebar_second"></div> ::after </div> ::after </div>
So yes, this issue is still live and #8 solved it for me.