Details
-
Type: Bug
-
Status: Open
-
Priority: Trivial
-
Resolution: Unresolved
-
Affects Version/s: 4.7.15
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:Developer Doc
-
Funding Source:Needs Funding
-
Verified?:No
Description
Discussion in CRM-11193, CRM-11043 & CRM-9993.
Currently running into some issues with Google geocoding when using civicrm_api3('Contact', 'Proximity'). Instead of returning an API error or throwing an exception, the result is printing fatal.tpl and abend.
What's the best way to make this consistent to other errors within API calls? Can we throw the exception from CRM_Core_Error::handle() when called?
See also CRM-20185?