Fixed for 4.2.22

Changes have been made in Git (master):

commit 1a79f02f61287123ce68ac85c27d07144bf3b3c6
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Sun, 29 Oct 2017 12:58:55 -0400

Bug: 14719 Fix filtering on returnFields.

  M lib/Api.php

https://github.com/horde/turba/commit/1a79f02f61287123ce68ac85c27d07144bf3b3c6

Changes have been made in Git (FRAMEWORK_5_2):

commit ff2a01d301042b36df1c50c04a5a023ade03f496
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Sun, 29 Oct 2017 13:02:45 -0400

Bug: 14719 Fix filtering on returnFields.

  M lib/Api.php

https://github.com/horde/turba/commit/ff2a01d301042b36df1c50c04a5a023ade03f496

Confirmed.

Update: function works partially.

It seems like all fields are returned always but some unrequested 
fields are not set to values (like workPhone in above example).

On the other hand, some not requested fields will always be returned 
(e.g. department and company).

It seems like this method was highly optimized for email use only.

For completeness sake I have my backends.local.php attached.

My code:


                $opts = array(
                        'returnFields' => array ('fax', 'firstname', 'lastname'), // works not
                        'fields' => array ('lastname'), // works
                        //'count_only' => true, // works
                );

                $result = $GLOBALS['registry']->contacts->search('searchstring', $opts);

The output invariably comprises entries with all available fields, 
regardless of their name and content.

Turba's API has a search() method that accepts a number of different 
parameters. However, setting the 'returnFields' does not change the 
returned fields.