Sonya* Posted December 20, 2021 Posted December 20, 2021 I have created a new block based of Feed from Articles with Default Template. Then I have added the block two times on the page. One in the vertical and another in the horizontal position. As the result, both the blocks use horizontal view for display: If I use only one block on the page, I see the correct view. But if the same block is placed into both the positions, they both start to use the same view (horizontal). How to bypass it? SeNioR- 1
opentype Posted December 20, 2021 Posted December 20, 2021 Create two blocks in the ACP, so they aren’t treated the same.Â
Sonya* Posted December 20, 2021 Author Posted December 20, 2021 (edited) I see. We already have two orientations in the template: {{if !empty( $records ) }} <h3 class='ipsWidget_title ipsType_reset'>{$title}</h3> {{if $orientation == 'vertical'}} <div class='ipsPad_half ipsWidget_inner'> this is a vertical view </div> {{else}} <div class='ipsWidget_inner'> this is a horizontal view </div> {{endif}} {{endif}} But the orientation is ignored (because of caching?). It is weird to have two blocks to handle different views, while we already handle the orientation views in the block template itself... I would say, it is a bug, where orientation of the block is not saved in cache. Edited December 20, 2021 by Sonya*
Sonya* Posted December 20, 2021 Author Posted December 20, 2021 It is even worse 😞 We cannot use the same block in horizontal AND vertical position even on different pages. If it is cached as vertical first, it will be displayed as vertical throughout the entire Suite. The actual position is ignored. If it is cached as horizontal, then it will be displayed as horizontal. It looks like having the same block in vertical and horizontal position is not possible. Not on the same page, neither on different pages.
Marc Posted December 20, 2021 Posted December 20, 2021 I have created a bug report for this for you, so that it can be taken a look at for you
Solution Marc Posted March 8, 2022 Solution Posted March 8, 2022 A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix. Sonya* 1
Recommended Posts