Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Hi,
My website looks fine in both Edge, Chrome, and Firefox but it seems to be displayed very wrong and awkwardly when using Internet Explorer.
I recently opdated to PHP 7.0 so this might have something to do with the situation.
We only just realized this error.
The problem mostly excists in the “full width” elements.
Website: weldadvice.dk
Hi Thomas
It’s possible this is related to Flexbox. Try setting Use Legacy Layout Engine to Always. You’ll find the setting at SettingsPage BuilderLayout.
Hi Andrew,
I made the change yesterday but it didn’t resolve the issue unfortunately.
Thanks. Please, edit the page in Page Builder, click the Layouts tab the Import/ExportDownload Layout. Upload the layout to wetransfer.com (no email address is required) or a similar sharing site and send us the link.
I’ll upload the front page and “Contact” page.
https://we.tl/t-5TQLUsaIs9
Hi Thomas,
Thank you for the exported layouts.
Unfortunately, I’m having trouble replicating this issue with the provided layouts. I can however reliably replicate this issue on your website. Hm. I notice you’ve sent the gradients to contain. Does the background display correctly in IE 11 if you set the Background Image to display as Tiled Image or Cover instead?
Hi Alex, the background isn’t the problem in IE. It’s the full width slider and layers. And also the buttons in the top of the frontpage.
Do you think changing the background settings will fix some of these issues?
Hi Thomas,
The other slider and SiteOrigin Image widgets on your home page appear to not be working as a result of a lazy loading plugin. Please try temporarily disabling that to see if that helps.
It’ll fix the display issue with the background on that specific row.
I’ve disabled the lazy loading plugin but that didn’t fix my images in IE.
It still looks okay when I set the background to “cover” but it doesn’t seem to change anything In IE. :S
Oh wait. It fixed some of them a little bit. They’re just small now, haha.
Hi Thomas,
Great to hear that helped.
There are two empty columns that are taking up a significant amount of space in that row. To make the images larger, you should remove them. We recommend using row padding to add space to the sides of the row.
Regarding the slider on the home page, pleas reach out to Meta Slider directly to see if there are any known issues with IE 11.
I’ve had an issue with the images not being centered when removing the manual padding. But that’s a story for another day. I suppose the small images will have to do for now.
I will contact the slider plugin regarding the slider.
Changing the background settings to cover did not fix the weird look in IE by the way.
Now, for one of the most important things. The button widgets in the top right corner is almost completely hidden in IE. Can this be fixed?
Hi Thomas,
Can you please show me a screenshot of the images still having issues? Please note that we currently don’t support attachments so you’ll need to upload the screenshot to an image hosting service such as Imgur and vgy.me.
That’s as a result of the following custom CSS you’ve added to WP AdminAppearanceCustom CSS:
#masthead .hgroup #header-sidebar { margin-top: -54px; }Hi Alex,
The buttons in the top right is visible in IE after deleting the CSS. Thanks! Even though it doesn’t look as cool in chrome anymore.
Front page is set to tiles. Contact page is set to contain.
IE Contact page
https://i.vgy.me/kgRHzT.jpg
IE Front page
https://i.vgy.me/EQSpnn.jpg
Chrome Front page
https://i.vgy.me/iF16Ez.jpg
Chrome Contact page
https://i.vgy.me/sPdSKW.jpg
Best regards
No wait I think it might be working!
Let me check…
Yes everything is working in your end now. I think the problem lies within Weglot, my translation plugin. Both my main slider and the full width images are somehow affected by the Weglot plugin :S
Hi Thomas,
I’m sorry to hear that. We’ve found the best results with WPML or Polylang.