Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Major
-
Resolution: Duplicate
-
Affects Version/s: 4.7, 4.7.1, 4.7.2
-
Fix Version/s: Unscheduled
-
Component/s: None
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
Description
4.7 introduced regression to geocoding functionality.
After upgrade from 4.6.11 OpenStreetMaps/Yahoo geocoding stopped working.
New contacts got no mappings and there are no errors logged except the following pop-up:
Unsupported Locale Unsupported locale specified to parseStreetAddress: en_AU. Proceeding with en_US locale.
"Street Address Parsing" is ticked/selected under Administer --> Localization --> Address Settings.
"Geocode and Parse Addresses" job hangs (never finishes) when configured as
geocoding=1 parse=1 throttle=1
Perhaps geocoding job needs "limit" parameter to restrict maximum records to geocode in one run.
When job invoked with
start=NNNNN end=NNNNN
to limit it to one record it logs
Parameters raw (from db settings): geocoding=1 parse=1 throttle=1 start=17624 end=17624 Parameters parsed (and passed to API method): a:6:{s:7:"version";i:3;s:9:"geocoding";s:1:"1";s:5:"parse";s:1:"1";s:8:"throttle";s:1:"1";s:5:"start";s:5:"17624";s:3:"end";s:5:"17624";} Full message: Finished execution of Geocode and Parse Addresses with result: Success (Addresses Evaluated: 1 Addresses Geocoded: 0 Street Addresses Parsed: 0 Following is the list of contacts whose address is not parsed: ...
I'm not sure how to troubleshoot further...
Attachments
Issue Links
- duplicates
-
CRM-19784 Yahoo Placefinder service appears to have EOL'ed
- Done/Fixed