David Matthew

I’d recommend disabling all plugins and seeing if the error still occurs. If it does, try switching themes. Often problems like this can only be solved via a process of elimination. Let me know how you get on.

Hi growup84, something is intercepting the widget and manipulating the iframe embed code before it is rendered. This wouldn’t be anything to do with the Ventus plugin itself, so I’m really not sure. I can only confirm that the code max-width: 100%_epi_ is not part of Ventus.

Hi terravolt, thanks for the feature suggestion! If it’s possible to add to the widget I’ll include it in a future release and update this thread to let you know. Thanks again, David

Thanks so much webb64b, I really appreciate the review!

Thank you a4jp, I absolutely will add that to the next update which is coming shortly (time constraints mean I haven’t gotten around to it yet).

Thanks again for your input, I really appreciate it.

Hey @jakours2, sure thing. Head on over to my website and you’ll see it. I have a test page set up which shows the Ventus shortcode in action, and in the sidebar you’ll see the widget: https://davidmatthew.ie/ventus-test

Hi khoavo,

Thank you for the helpful screenshots.

Can you confirm if this still happens in Chrome when the spot forecast isn’t active?

You might have a quick read too of this support thread, which may be related: https://www.ads-software.com/support/topic/map-centers-properly-only-after-refresh/

Thanks,
David

Hi a4jp,

I will be adding an option for lazy-loading the iframe in the next release, which should be in the next few weeks as soon as I get the chance. This will hopefully help with any pagespeed issues.

I don’t have control over the internal loading or rendering of the iframe content though, only the parameters that initialize it.

Hope this helps.

Thanks,
David

Hi kocur, because the widget title is just a heading element (most likely a <h2>, but that can be theme-dependent) for the Ventus shortcode you just need to add a <h2> element before it to achieve the same effect, so it didn’t feel it was worth adding as an extra parameter.

Hope this helps and explains why I didn’t implement it.

If you have any other questions I’ll be happy to help.

Thanks,
David

Hi @twgerber yes this is with windy itself and the leaflet library it uses; I don’t have access to the underlying windy code/server config.

I am planning however to include a lazyload option for the iframe in the next release, and I’m hoping it will help with pagespeed issues like this.

Hope this helps.

Thanks,
David

Thanks for letting me know of this behaviour @twgerber, I might need to look into adding some options related to scrolling.

The centering issue that you mention is usually only present with the spot forecast enabled (see this previous support thread), so it makes sense that it wouldn’t be reproducible when you disable it. However, it can also be affected by where the widget is placed relative to the viewport, so I think there may be other configuration options I might be able to add in future to aid with issues like this.

Thank you @twgerber for the review, it’s very much appreciated. ??

Thank you so much @ma3ry for the kind words! I really appreciate it. ??

Hi mahii-conception,

Can you confirm what version of the plugin you’re using?

From the page you’ve linked to it looks like you’re using the shortcode? If you could paste it here that would help.

Just a note that the forecast attribute can be set to true to display the spot forecast, otherwise it will remain hidden. From what I can see it looks like this has been set to true.

Thanks,
David

Hi Christian, thank you for the feedback and I’m glad to hear you got the issue resolved in the end!

Please let me know if I can offer any further assistance.

All the best,
David