tuxlog

Hello,

can you please give me the coordinates ot the location for this widget.

I have installed MediaPress now on my Testsite. Unfortunateyl I can not visit your site because it is under maintenance. Where exactly do you want the smilies to be added? I only find text editor fields and no rich editor fields.

Would be nice to have a bit more information about your requirement.

Thanks, tuxlog

Hello,

I will have a look at it during the next days and give you a feedback.

Hello Kurt,

the new version I just released should fix the warnings.

Hello Steve,

yes, I already fixed this for the next release. It is just a warning you do not have to worry about. Seems you have setup to show all warnings and not only errors which leads to the warnings are showing up.

I will publish the fix in the next few days and then the warnings should be gone.

Cheers, Hans

I just sent you an email. It seems you set the maxwidth and height to 0 which hides the smilies. Setting it to e.g. 30×30 and the smilies are displayed again.

Hello dariotoby,

can you please give me the versions you are using? Version of WordPress, WPFORO, wp-monalisa, so I can try to reproduce the problem.

Thanks

You can set the cache time in the field “Refresh cache after” in seconds (e.g. 7200 = 2 hours) . This is a per widget/location setting. Every widget can have a different cache time.

Hello Kurt,

thank you for the hint. Those messages are no errors but just notices from php. I just fixed it for the next release.

Cheers

Sorry, seems I missed your request, just saw it.

Well, it slows down because if the weather data has to been updated it will <number of locations> requests to fetch the current weather data. The only solution is to setup long cache times to avoid reloading the weather from the weather data provider every time the page is loaded.

E.g. if you have 200 locations there will be 200 request in the background to fetch all the data and this takes some time.

Thank you, so I see nothing special about Nashville conerncing timezones, it is GMT-6 = CST. Looking at the plugin if you activate localtime the time will be taken from your blog with the following function calls:

$w['blogdate'] = date_i18n( $wpf_vars['fc_date_format'], $ct );
 $w['blogtime'] = date_i18n( $wpf_vars['fc_time_format'], $ct );

If you do not activate local time the time from the weatherprovider is taken.

Can you check if your server has the correct time after switching daylight saving and have a look at your WordPress setup if it has the correct timezone.

Maybe this can be the reason. I just checked some of my wp-forecast installations and it seems to work.

Cheers, Hans

Hi Rob,

do you use OpenMeteo or Openweather and please give me the location of the weather widget, so I can try to rebuild the problem.

Thanks.

Hey Rob,

just released a fixed package.

Cheers

Hi Rob,

thank you very much for your analysis and results. Indeed it seems the metric value of the precipitation in openmeteo data is divided two times by 25.4 and thus the wrong inches are calculated. I will try to fix this asap and release a new package.

Thanks again, Hans

The plugin has an inbuilt cache for the weather data and it will load the weather data for each location/widget if the cache has expired. You can set the duration in seconds until the cache expires for each location using the field “Refresh cache after”.

So, it will load the weather data for all widgets the cache has expired, when you load the page.

Hope it helps.