• Resolved kbowson

    (@kbowson)


    Hi guys,

    I have read through your WP support tickets pretty extensively… and have read through your documentation (here: https://docs.wp-rocket.me/category/32-lazyload). I’ve seen people comment similar things to what I’m asking (ex: https://www.ads-software.com/support/topic/does-this-work-maybe-outside-loop-issue-footer/). It seems in most of those support tickets, you say that it’s some custom function that your plugin is unable to register.

    But, it does not seem like that in my case. Here’s why:

    REASON #1: the plugin work on the same functions… on different pages. For example, it works here: https://theunbox.com (a page)… but NOT here: https://theunbox.com/tinker-crate-reviews/ (a post).

    REASON #2: the class is being added lazy loading (more specifically, it’s class=”lazyloading”)… this is something I’ve asked in another support ticket

    IN SHORT:

    The plugin recognizes the images in BOTH instances, but only works correctly in one of the two.

    We’re loading a ton of images at the bottom of the page, which is crushing load times on mobile… so any help would be GREATLY appreciated.

    K

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author WP Media

    (@wp_media)

    Hi,

    Looking at the pages provided right now, I don’t see our lazyload active at all, which makes it difficult to debug.

    If I understand correctly, you’re talking about the MUST-READ NEW POSTS section at the bottom?

    Thread Starter kbowson

    (@kbowson)

    Hah crazy timing! First time the plugin has been off for weeks! It’s back on now!

    There are 3 sections that lazy load doesn’t work correctly with…

    1 = must read new posts
    2 = trending posts
    3 = the menu

    Plugin Author WP Media

    (@wp_media)

    For 1 and 3, I don’t see any of the code we normally had to perfom the lazyload (data-lazy-src notably). That means the PHP code used to create the image HTML tag is not using one of the WordPress functions.

    From what I gather the theme is either Divi or Extra? It might be necessary to raise the issue on their side too.

    For 2, the slider is using the image as a background-image in CSS on the container div, which we don’t support at the moment.

    Thread Starter kbowson

    (@kbowson)

    Correct, we are using Extra (which uses Divi). Let’s focus on that must-read posts section… why would it be that that section would lazy load on the homepage (https://theunbox.com)…. but NOT on the posts pages: https://theunbox.com/sprezzabox/.

    It’s being loaded the exact same way, through the exact same PHP on both pages.

    PS: their support is completely inept.

    Plugin Author WP Media

    (@wp_media)

    I see lazy load is working in the post content, so it’s not a problem if it being deactivated page wide.

    The only thing I can think of right now would be that somehow the generating code is different for the homepage and for the posts, but at that point I would need to see the code the understand why it’s behaving like that

    Thread Starter kbowson

    (@kbowson)

    They are both using the exact same shortcode. The code should be identical. How can I help you to troubleshoot further?

    Plugin Author WP Media

    (@wp_media)

    Which Extra module are you using to display this section?

    Thread Starter kbowson

    (@kbowson)

    The blog module

    Thread Starter kbowson

    (@kbowson)

    Hi, can you please follow up on this?

    Plugin Author WP Media

    (@wp_media)

    Hi,

    We updated the plugin to 2.0, which should catch more images and be more compatible. Please update and see if it works now for your case.

    Thread Starter kbowson

    (@kbowson)

    Hey guys,

    sorry. I meant to reach out to you yesterday. I updated yesterday and everything started lazy loading! Was awesome!

    Thank you!

    • This reply was modified 6 years, 2 months ago by kbowson.
Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Lazy Load NOT working in footer, on specific pages’ is closed to new replies.