Last modified: 2013-01-08 00:15:20 UTC
Some pages with apperently correct 'address' information sometimes fail to #geocode (actually I passed the wrong field in a template, so it's geocoding correctly now, however...). I tried lots of things to force the 'update' of the coordinate data on the problem page, including "Data repair and upgrade". When I ran this, however, runJobs.php gave the following error when it arrived on the problem page: 2011-10-04 19:08:24 SMWUpdateJob Dip._Biologia_Cellulare_e_dello_Sviluppo t=809 good PHP Fatal error: Call to undefined method SMWDIError::getLatitude() in /home/www/htdocs/CellLinesWiki/extensions/SemanticMaps/includes/queryprinters/SM_QueryHandler.php on line 278 Fatal error: Call to undefined method SMWDIError::getLatitude() in /home/www/htdocs/CellLinesWiki/extensions/SemanticMaps/includes/queryprinters/SM_QueryHandler.php on line 278 Here, runJobs.php fails, and the status of the "Data repair and upgrade" job is left at 50%. Firing it off again hits the same problem again: Although I fixed the geocoding string, I don't think this should be dieing in this way. I'm not sure if this is an SMW bug or a Maps bug... I figure Jeroen will know. Here is the text of my template in case it's relevant: http://sandbox.referata.com/wiki/Template:Laboratory and here is the calling page (fails to #geocode if you don't pass the city field correctly): http://sandbox.referata.com/wiki/Dip._Biologia_Cellulare_e_dello_Sviluppo Cheers, Dan.
I am not sure whether this is an SMW or an SMW bug either. Clearly, SM treats an objects as a coordinate that really is an error. Most likely, this just means that SM forgot to check if the object has errors before accessing it. On the other hand, it could be that SMW returns such an error object in a place where it promises to not do this. Then it would be an SMW issue. But the entry point clearly is SM here, so I reassign this accordingly and let Jeroen decide whether he thinks it should be changed back to SMW.
Hay Dan, sorry for not getting back to you earlier. I remember fixing something like this at least some months back. Are you sure it is still present in the latest releases?
I'll have to dig up access to the old wiki where I was seeing this problem. Please give me a few months to get down to it (sorry!), Dan.
Assuming this is fixed
