[Tickets #10804] Re: some issues with the new weather block

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10804
------------------------------------------------------------------------------
  Ticket             | 10804
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | some issues with the new weather block
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-11-29 03:34) wrote:

This is exactly why the timeobjects driver sets the units after  
getting the weather driver from the injector. The units *are*  
determined on demand. When we request a value that can returned in  
different units from either the current or period objects, the units  
are checked and the appropriate units are returned.

I'm reverting the changes because $_driver is actually never set in  
the timeobjects driver anyway, and these changes break setting the  
correct units.  Also, getForecast() doesn't allow you to pass the  
units...not sure where you see this at?

I made changes not too long ago that deal with Google returning  
whatever units it seems fit. I cannot reproduce this locally, using  
the calendar block and the weather block, with the Google driver or  
the Wwo driver (which is what the OP is using). I've tried using  
Germal locale, with both European and US locations.