Documentation: lookup_contact_by_name with quickfind (API) mode, or no mode set fails: Contact getquick is removed as of CiviCRM 5.66

[RositzaDikova]

Problem: The civi banking "Default Options" plug-in does not provide any suggestions (fails), when for lookup_contact_by_name no mode is set, or quickfind (API) mode is set.

Fix: Make sure you include specifically "mode":"sql" in your "Default Options" configuration, or plugins using lookup_contact_by_name
"lookup_contact_by_name": {
"mode": "sql",

BankingLookup.php (api/v3):

 // run the actual search
  if (empty($params['mode']) || $params['mode']=='getquick') {
    $contacts_found = _civicrm_api3_banking_lookup_contactbyname_api($name_mutations, $params);
  } elseif ($params['mode']=='sql') {
    $contacts_found = _civicrm_api3_banking_lookup_contactbyname_sql($name_mutations, $params);
  } else { // OFF / invalid
    $contacts_found = array();
  }

Switch menubar search to use APIv4 & delete deprecated v3 'getquick' action #26676

In doubt the BankingLookup.php will get updated to reflect this, but the issue might help users, if they fall in this scenario/situation.

[glanzel]

There are two Examples (Standardoptionen.civbanking and Zuwendung erstellen.civbanking) in the configuration_database without an "mode" set for "lookup_contact_by_name"
Maybe this should get fixed so people dont use these and think it should work.

[bjendres]

Thanks for the comprehensive analysis @RositzaDikova and @glanzel.

I think we should add a warning to people still using the getquick mode on CiviCRM >= 5.66.

Additionally, we could investigate if APIv4's Contact.autocomplete action could be a replacement.