Support » Plugin: Lazy Load for Videos » Lazy load with parameters

  • Hi

    I have a WordPress divi site with embedded youtube videos through module in the builder.

    I have a little script that adds “&hl=da” to the url to show controls etc. on video in danish.

    But when I use your plugin that gets stripped and it shows with english controls on play.

    Do you have a solution to fix that?

    Please note the lazy load plugin is deactivated at the moment beacause of that.

    Thank you.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author kevinweber

    (@kevinweber)

    What version of the plugin are you using? Make sure to use the latest version. If you just updated the plugin version, try the page in an incognito window or clear your browser cache to make sure your pages loads the latest JavaScript.

    For me, it works. I tested the following URL in a regular WordPress Youtube Embed block: https://www.youtube.com/watch?v=X5d3g4bBASM&feature=oembed&rel=0&hl=da

    Maybe Divi modifies the URL somehow but then I can’t do much about it. I don’t have Divi and can’t test this scenario.

    Thread Starter hassenkam

    (@hassenkam)

    Hi,

    I’m running the latest version of everything.

    As you can see on the site it works now, with lazy load deactivated, but when I active it, it removes the language paramater.

    Isn’t there any workaround to make it work … somewhere in your code maybe?

    and mayby in the future you can add a custom field for parameters to attach?

    Plugin Author kevinweber

    (@kevinweber)

    As I said, I verified it works on a normal WordPress theme on my own WordPress blog. I also verified this in code: Query params aren’t being stripped from the URL; the hl query param should stay as part of the URL, so I think it has to do with either Divi, your theme or some other plugin. You can try it out using a non-Divi theme and see if it works. At this point I don’t see how I could fix this for you unfortunately. You could ask some other developer to look at your WordPress setup and figure out what exactly is causing the issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.