LDAP Views: Warning: array_multisort(): Array sizes are inconsistent in ldap_views_plugin_query_ldap->execute()

This patch fixed the issue for me. There appeared to be an extra call_user_func_array('array_multisort', $params);.

I committed this to the 1.x and 2.x branch. Thanks.

This issue still exists in the latest 7.x-1.x-dev

Same problem in 7.x-2.x-dev described here: http://drupal.org/node/1773850

Due to no feedback in over three years I presume no one else is seeing this. Please reopen with more information otherwise.

My issue was related to empty values for certain fields so if you sorted on those fields you ended up with an incomplete array of data as the empty fields were being left out. I don't have a patch for this but here is what I did:
ldap_views -> ldap_views_plugin_query_ldap
Basically if the alias doesn't exist in the entry then I still continued through to add it to the sort_fields data with a null value.

if (is_array($entry) && array_key_exists($alias, $entry)) {
          if (is_array($entry[$alias])) {
            switch ($field->options['multivalue']) {
              ...
          if (array_key_exists($alias, $sort_fields)) {
            $sort_fields[$alias]['data'][$key] = $entry[$alias];
          }
        }

if (is_array($entry)) {
          if (array_key_exists($alias, $entry) && is_array($entry[$alias])) {
            switch ($field->options['multivalue']) {
              ...
          if (array_key_exists($alias, $sort_fields)) {
            $sort_fields[$alias]['data'][$key] = empty($entry[$alias])? null : $entry[$alias];
          }

Also worth mentioning that this is in version 2.3

@tklawsuc: Please don't simply comment on closed issues, it's not a guarantee that someone notices that and this issue is extremely old. Either reopen the issue if it really is the same issue or create a new one. If you create a new one you can still easily link to this issue through the "Related issues" reference if you think it's related.

@grahl thanks for the notice. I was just posting it here for people to have as reference in case they stumble on this link searching for the exact same issue as the title of this error...as in my case.