| Summary | Fatal error in Horde_Service_Weather_WeatherUnderground |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | jan (at) horde (dot) org |
| Created | 09/17/2015 (3586 days ago) |
| Due | |
| Updated | 09/17/2015 (3586 days ago) |
| Assigned | 09/17/2015 (3586 days ago) |
| Resolved | 09/17/2015 (3586 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
stashed on a local topic branch.
should be a Horde_Service_Weather_Forecast_Base object. That, and
the request for the radar image doesn't pass the forecast length
currently, so the check for lastLength fails, even though we didn't
change any user prefs :)
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Assigned to Michael Rubinsky
Queue ⇒ Horde Framework Packages
Summary ⇒ Fatal error in Horde_Service_Weather_WeatherUnderground
Type ⇒ Bug
State ⇒ Assigned
WeatherUnderground backend is broken. I know, it doesn't make any
sense, but at least that's what bisect tells me.
( ! ) Fatal error: Call to a member function limitLength() on array in
/home/jan/horde-develop/framework/Service_Weather/lib/Horde/Service/Weather/WeatherUnderground.php on line
242
Call Stack
# Time Memory Function Location
1 0.0001 240208 {main}( ) .../index.php:0
2 0.1071 3044288 Horde_Core_Block_Layout_View->toHtml( ) .../index.php:35
3 3.3834 10484384 Horde_Core_Block->getContent( ) .../View.php:98
4 3.3834 10484568 Horde_Core_Block->_call( '_content', '', ???
) .../Block.php:175
5 3.3834 10485472 Horde_Block_Weather->_content( ) .../Block.php:278
6 3.3881 10590984 Horde_Service_Weather_WeatherUnderground->getForecast(
'zmw:00000.10.10326', '7', ??? ) .../Weather.php:149
7 3.3881 10591152 Horde_Service_Weather_WeatherUnderground->_getCommonElements( 'zmw%3A00000.10.10326', '7'
) .../WeatherUnderground.php:128
What I don't understand at all is, how the limitLength() could have
ever worked with $this->_forecast being an array since always.