igorkalders

Thanks for taking the time to answer, and also for the help on trying to solve this issue:

https://github.com/dannyvankooten/recent-facebook-posts/issues/30

??

@mjbehrii How did you get to your fix? Did you get an error message about what was wrong? Is it mandatory to specify a version for FB api communication, or is the plugin incompatible with the most recent version?

In the former case, I guess it’s easy to create a PR to have this fixed in the plugin, but in the latter case, it’s a matter of time before the plugin breaks again.

The plugin is currently disabled because I’m relying on some custom module I created to fix the VC lazy loading on the server side.

I don’t think you need a sample to tell you the issue, though. Lazy loads generally work by outputting the data-src on the server side, and transforming that to a background-url on the client side. Your plugin does both the transformation to data-src and back to background-url on the client side. Because you’re never sure when javascript is executed, the browser may already be loading the images when your script triggers.

Also note that (1) VC outputs styles in-page, so they are available at page load time and (2) your plugin scripts might be loaded after that because of WordPress optimizations