Kommentare zu: Checkliste für wp-forecast / Checklist for wp-forecast

Von: Octavio

Octavio — Wed, 03 Nov 2010 14:19:37 +0000

Thanks a lot, that worked! Glad you liked my photos.

regards

Von: webmaster

webmaster — Wed, 03 Nov 2010 06:09:27 +0000

hello Octavio,

I suppose the daylight saving for the selected location changed (in the accuweather data) and thats why the time changed. if you want a different time just use offset 60. i have just googled a bit about timezones and brazil and it seems there are different timezones in brazil. i remember that we have had the same problem with new zealand (more than one timezone too), accuweather did deliver the wrong timezone/daylight setting and therefore wp-forecast calculates the wrong time.

regards, hans

p.s. great photos at your site…congrats

Von: Octavio

Octavio — Tue, 02 Nov 2010 20:46:36 +0000

Hi, I have your plug-in and love it, but since yesterday I noticed that the current time shown is 1 hour early. Could be something to do with summer savings time, but it’s weird because it wasn’t happening before, when we already were in summer savings. Is there a way to fix it? The time here at this time of the year is UTC -2. I have current time checked with 0 offset.

thanks

Von: wordpress « wp-forecast 3.0 beta – goes Multiuser « Tuxlog

wordpress « wp-forecast 3.0 beta – goes Multiuser « Tuxlog — Sat, 03 Jul 2010 05:26:57 +0000

[...] Eine Checkliste um bei Problemen die Möglichkeiten der Datenübertragung zu prüfen. [...]

Von: webmaster

webmaster — Fri, 25 Jun 2010 03:48:18 +0000

hello Lincoln,
thats the only known problem with wordpress 3.0. you can fix it -until I release the 3.0 version- changing the unserialize to maybe_unserialize in any of the lines you get the warning from.

regards, hans

Von: Lincoln Barbour

Lincoln Barbour — Thu, 24 Jun 2010 18:52:06 +0000

Thanks for making such an awesome plugin. I’m having some kind of cache issue. Every so often when the site loads up, I see this error message:

Warning: unserialize() expects parameter 1 to be string, array given in /home/…/wp-content/plugins/wp-forecast/wp-forecast.php on line 173

Warning: unserialize() expects parameter 1 to be string, array given in /home/…/wp-content/plugins/wp-forecast/wp-forecast.php on line 277

Warning: unserialize() expects parameter 1 to be string, array given in /home/…/wp-content/plugins/wp-forecast/func_accu.php on line 268

Then, if hit reload or go to another page, the weather shows up fine.

Any thoughts?

Lincoln

PS: Here is the debug call stack

Start of MAIN
End of MAIN
Start of function widget_wp_forecast_init ()
End of function widget_wp_forecast_init ()
Start of function wp_forecast_init ()
Start of get_wpf_opts (A)
End of get_wpf_opts ()
End of function wp_forecast_init ()
Start of wp_forecast_admin_init ()
End of wp_forecast_admin_init ()
Start of function wp_forecast_css ()
End of function wp_forecast_css ()

Von: webmaster

webmaster — Sun, 14 Mar 2010 08:55:43 +0000

hello don,
yes it is. you can set the refresh interval with the option “Refresh cache after” in seconds. E.g. 3600 means once an hour.

regards, hans

Von: Don Luciano

Don Luciano — Sun, 14 Mar 2010 08:29:10 +0000

Is it possible to cache the data and only refresh once in an hour. We’re getting lazy website loading time because of wp-forecast.
Thank you.

Von: webmaster

webmaster — Wed, 05 Aug 2009 06:01:58 +0000

hi eglin,
does this error only show with wp-forecast or also in the dashboard? this matter seems to be known, take a look at the wordpress forums and it seems a problem with the provider and wordpress combination. which transport method did you try? does it show up with every transport?

Von: elgin freeman

elgin freeman — Tue, 04 Aug 2009 20:15:27 +0000

I am having a problem getting wp-forecast to work on my WP site. This error shows up in Incoming Links: RSS Error: WP HTTP Error: 13: Permission denied

Can you help?

Thanks. . .