When click on the location, a call to http://api.openwathermap.org is made creating mixed content resulting in the browser blocking the script.
I was suggested to remove and recreate the Widget. This has no effect as the call is hard coded in tagdiv_theme.js (min).
You can check this in the console here https://insidetravel.co.za/weather-test/ or on the homepage
Hi,
We are aware of the issue with the weather widget. Please note that the developers are currently working to fix the problem, and hopefully this will get fix as soon as possible.
Thank you for understanding!
Any progress on this?
Hi,
Are you still experiencing problems with the weather widget? It is working properly now on your test page
– https://www.screencast.com/t/WYa8G5JVFM
And on my end
– https://www.screencast.com/t/dIFYsbli
Thanks
I am still getting mixed content on the home page (https://insidetravel.news) -> https://www.screencast.com/t/t24ybrBx
Hi,
I have tested the weather widget function, but everything is working properly. Please try as a test to disable all your plugins except the ones provided with the theme, remove the weather widget from your page and clear any caching installed. Then add the widget again and check to see if it is working properly. Please let us know how it goes.
If the problem is still there, maybe you have not made the necessary modifications when moving to https
You could check these few resources for more information
– http://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/
– https://css-tricks.com/moving-to-https-on-wordpress/
– https://yoast.com/dev-blog/move-website-https-ssl/
You can also check our forum for some insight on ssl:
– https://forum.tagdiv.com/topic/moving-to-ssl/
Thanks
Thanks for the above info 🙂
We have move quite a lot of websites to https in the last couple of months.
line 10948 (latest build) of tagdiv_theme.js
var weather = 'http://api.openweathermap.org/data/2.5/weather?lat=' + tdWeather._currentLatitude + '&lon=' + tdWeather._currentLongitude + '&units=metric&lang=' + tdWeather._currentItem.api_language + '&appid=' + tdWeather._currentItem.api_key;
this is where I think the issue lies. Openweathermap API does not use SSL. (And I don’t think they intent to unless you pay $180/m)
Hi,
It seems that is the case yes. Maybe you should look for a weather plugin that you can use in this situation and hopefully work properly for you.
Thanks
We were using another weather plugin prior to TagDiv adding one …
which I think was this one:
https://wordpress.org/plugins/awesome-weather/
Loved it. Still love it 😉
oddly the version of the TagDiv weather widget with Newsmag 3.1 works with https just fine as we are still using that on numerous sites with no https issues whatsoever.
