Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.1

Bug #20179 API host ws.geonames.org is no longer valid
Submitted: 2014-01-17 19:34 UTC
From: stevehunter Assigned: stevehunter
Status: Closed Package: Services_GeoNames (version 1.0.1)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 21 + 23 = ?

 
 [2014-01-17 19:34 UTC] stevehunter (Steve Hunter)
Description: ------------ This package uses the host ws.geonames.org whereas it should be using the newer api.geonames.org. As of 17th Jan 2014, ws.geonames.org seems to have been removed from DNS, causing the following exception to be raised: Services_GeoNames_HTTPException: Unable to connect to tcp://ws.geonames.org:80. Error: php_network_getaddresses: getaddrinfo failed: Name or service not known The fix is to change: public $url = 'http://ws.geonames.org'; to this: public $url = 'http://api.geonames.org'; in Services/GeoNames.php

Comments

 [2014-02-05 08:14 UTC] doconnor (Daniel O'Connor)
Can you open a pull request please?
 [2014-02-05 18:16 UTC] stevehunter (Steve Hunter)
No problem, pull request opened now
 [2014-02-05 18:22 UTC] stevehunter (Steve Hunter)
Just to note that although here https://groups.google.com/forum/#!topic/geonames/UmPdTGMHjrU the service maintainers state that ws.geonames.org has been disabled, it now appears to be resolving again.
 [2014-02-05 22:49 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: stevehunter
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.