This topic has 5 replies, 2 voices, and was last updated 1 years, 5 months ago ago by Dee
Screenshoot: https://prnt.sc/Liq9LnDEL5Je I have removed the previously use image slider and used another element for the slider. But still it’s the same.
Hello Dee,
Thank you for contacting us and for using XStore.
Please try to use the next custom CSS code:
.elementor-widget-etheme_banner_carousel .swiper-entry:not(.swipers-couple-wrapper) .swiper-wrapper {
max-height: 660px;
}
Kind Regards,
8theme team
Though it fixed the issue on desktop, on mobile there is whitespace. So I resize the browser width downward from the max I could have on my desktop. when the width is less than around 1444px it still maintains the 660px max-height. Slide itself getting smaller and smaller but the whitespace is there : (
I don’t think having max-height will solve the problem. I need something solid as a solution. Btw is this my problem or theme itself?
Hello Dee,
Thank you for your response.
We do not have this problem on our test site.
In order to troubleshoot the issue you are experiencing, we suggest that you first try disabling all third-party plugins (including cache plugins) that are not bundled with XStore. You can refer to the following link for a list of included plugins: https://www.8theme.com/documentation/xstore/plugins/included-plugins/ . Additionally, please clear the cache of your browser and check again. It is possible that one of the additional plugins is causing the problem.
Please let us know the result of this test.
Kind Regards,
8theme team
The issue happened to be related to Jetpack. First I tried to disable the minified CSS feature and tried with the cache cleared. No good. Then I deactivate the plugin and boom issue is fixed. Probably because of the lazy load feature which was enabled by Jetpack. The issue is sorted and you can mark the topic as “Solved”
Tagged: huge space, slider, themes, woocommerce, wordpress
The issue related to '‘Do you have any idea what makes this huge space under the slider ?’' has been successfully resolved, and the topic is now closed for further responses