dbhynds

Bizarre. For reasons I don’t fully comprehend, it looks like the it’s loading the largest size image, instead of the correct one as specified by the srcset.

The plugin I wrote implements Lazy Load XT for wordpress, but I didn’t actually write the javascript itself. (My plugin basically filters content and loads the .js and .css… with a few other bells and whistles.) It looks like whatever is going on is outside of the purview of what this WP plugin does. You might try following up with the creators of the .js plugin itself here: https://github.com/ressio/lazy-load-xt/.

Let me know if I can be of any more assistance.

Do you have the “Enable AJAX Navigation” option checked? You may need to tell lazyload to fire as the carousel advances. See the documentation here: https://github.com/ressio/lazy-load-xt/

Do you have the “Enable AJAX Navigation” option checked? What lightbox solution are you using?

Could you provide me with a link to your site? It’s possible that there’s nothing I can do about it, but I can at least take a look and see if I can diagnose it.

Without getting into a full discussion of the merits of mobile-first/responsive blah blah, I’ve decided to make it a priority to provide the user with a unified experience regardless of their device. One option you might consider for mobile devices is to lazyload elements before they come into view. Check out the documentation here… specifically the edgeY option: https://github.com/ressio/lazy-load-xt/#options

Hm. I see the problem in the video, but when I visit the link you provided, it works fine for me. What browser are you using?

I believe that if they’re in an <img /> tag, they should lazy-load like everything else. Does it not? Or are you loading SVGs inline? If it’s inline, I’m not sure there’s much that can be done about it.

Great suggestion! I’m not sure I’ll have time anytime soon to incorporate this feature. However, if you can find another plugin in the WP Plugin Directory that will do this, I suspect the two should work together fine in combination.

Not currently. That’s a feature I hope to implement in the future, but it’s not available at the moment.

I tried the setting the query_var to both resources/keywords and just keywords, but neither got me the desired result. In the end I just deleting the rewrite argument altogether from my CPT declarations.

If you could get this working, that would be amazing. Ideally the URL structure would be:
/resources/disciplines/corporate-giving/keywords/social-media/
or
/$post_type/$tax_1/$tax_term_1/$tax_2/$tax_term_2/

However, this would also work for me:
/resources/archive/disciplines/corporate-giving/keywords/social-media/
or
/$post_type->slug/$tax_1/$tax_term_1/$tax_2/$tax_term_2/

If that’s not possible, hopefully the client doesn’t make too much of a stink about it. If they do, I may have to find another solution. Anyways, I appreciate the help and the timely, thoughtful response.

It depends on how the bxslider is implemented, but based on what they show about it out of the box, this plugin should work on it. If it doesn’t, please view-source the page and copy/paste the HTML that it generates for the slider here. I’ll take a look and get back with ya.

So is the problem that the image is actually appearing too large (more than 640px) on the screen? Or that the browser is loading a larger image then scaling it down to 640px?

If it’s the latter, I think that’s because of the responsive image functionality that got implemented with the release of WP4.4, which I don’t want to mess with since that’s a pretty important feature. Though it is odd that it loads the smaller one without the plugin enabled.

That’s weird!

Can you view source and post the HTML that’s getting generated for the image? (Include the noscript tags, too, please.)

Thanks!

I believe this is now corrected. However, there is a console error with the bg images. Reference this thread: https://www.ads-software.com/support/topic/console-error-2?replies=6

I’ve got a bug report open with the creator of the plugin, and will update you when I hear more. In the mean time, I’m marking this resolved. Thanks for using my plugin and submitting a bug report.

Sorry for the delay in getting an update on this. I was moving and it sucked up all of my time.

Version 0.5.3 has a fix to your problem. Update it and let me know if it works, please. Thank you for your support and using this plugin!