Last modified: 2010-11-15 18:40:42 UTC
I installed the trunk copy 1.17alpha that you fixed for Bug 25872. (I can see your fix comments in the release notes) When I attempt to store a page with the following: {{#display_point:New York City}} - the save action hangs for a really long time and then I get the following message: "Fatal error: Parameter coordinates must be one or more valid locations." Then I tried the example off of your page at: http://mapping.referata.com/wiki/Maps_examples {{ #display_points: Moscow, Russia;New York City; Brussels, Belgium | icon=Green_marker.png }} The wiki hangs for a long time and then return the message: "Fatal error: Maximum execution time of 30 seconds exceeded in C:\xampp\htdocs\wiki\includes\HttpFunctions.php on line 981" Thanks. Corneel.
No changes have been made to the Maps extension following your bug report about the Http class. If the name of the class has changes in MediaWiki core, then the extension will fail. I'll have
... a look at it for the next release, to make sure nothing breaks. The issue you describe is caused by the geocoding of the provided address(es) failing. Make sure your proxy settings are correct, so the geocoding service is reachable.
(In reply to comment #1) > No changes have been made to the Maps extension following your bug report about > the Http class. If the name of the class has changes in MediaWiki core, then > the extension will fail. I'll have Note, backwards compatibility is maintained so the old HttpRequest will still work (but you should be using MWHttpRequest if possible). However with that said, Semantic maps used Http::get which is a wrapper around HttpRequest (now MWHttpRequest), so semantic maps should not have to change anything at all on that front.
(In reply to comment #3) > Note, backwards compatibility is maintained so the old HttpRequest will still > work (but you should be using MWHttpRequest if possible). However with that > said, Semantic maps used Http::get which is a wrapper around HttpRequest (now > MWHttpRequest), so semantic maps should not have to change anything at all on > that front. Oh, ok, that's nice. This bug report is purely about failing geocoding service then. I'm afraid I can't really do much about that. You can try switching the used geocoding service. I'm open to suggestions on how to improve the geocoding capabilities.
It seems the problem was that I was testing the code on a private server. I moved it to a public server and the Map extension is now working fine. http://semanticstreams.com/wiki117/index.php?title=New_York Thanks for all the help... I am new to this. :-) Corneel.
