@thepopularizer i believe this was already fixed. Are you using the latest version?
Yes, 2.4.1.
I just checked, and it seems to alternate from “background-image” to “background” upon force refresh. Most strange.
@thepopularizer can you share the url?
Certainly:
https://www.showcase.thepopularizer.com/location/
I just checked, and I see that if you’re logged out, it’s stuck on “background”. When I’m logged in, it switches from one to the other.
@thepopularizer Flying Images doesn’t process images if you’re logged in as admin.
Also, from testing locally, I can confirm them it respects both background and background-image.
Hm, that’s strange. It seems to be processing as I’m logged in as admin, *and* not respecting “background-image” for me:
View post on imgur.com
Shall I email you a login so you can check it out?
Same issue here, I just updated the plugin to the latest version (as of now), cleared the cache and hard-refreshed the page. No luck. Battled the issue via the use of !important inside CSS. The image in question is the hero bg-img.
https://beedelightful.com/learn-more/?kinsta-cache-cleared=true
-
This reply was modified 6 years, 4 months ago by
Marc Wiest.
@thepopularizer I checked it in detail. I can see that Flying Images don’t replace background-image to background. You can confirm it by looking at the source code http://tinyurl.com/wc3exhw
However, while checking through the inspector, looks like some script changed it back to background. Also added center -16px (this was not present in the source HTML). See http://tinyurl.com/v67mpqp
So I think some other plugin/theme is co nflicting with Flying Images’ lazy loading. I can see that it works fine if lazy loading in Flying Images is disabled.
Are you using any other plugin/code for lazy loading? If so disable it?
If this only happening to that particular image, try excluding it from lazy loading. Since it’s in the above fold, it’s better to exclude to improve performance.
I think I might know what it is. I’m using a parallax script (paroller.js). It may be rewriting the css for parallax purposes. Is there a way to make lazy loading compatible with it? Anyway, thank you. I’ll work around this issue for now.
@thepopularizer I’m not familiar with paroller.js and how it works. I don’t think I can support it
