After the upgrade to 6.6 I get this message when I go to check my account details:

    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/drupal-6.6/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/drupal-6.6/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/drupal-6.6/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/drupal-6.6/sites/all/modules/ldap_integration/ldapdata.module on line 355.

I tried disabling then uninstalling the module, then re-enabling it. No difference, still the same bug.

Comments

aloyr’s picture

aloyr commented

I got the same behavior on one of my sites as well... running 6.x-1.0-alpha2 of the ldap-integration module. I don't know if it matters, but I am querying against the active directory's global catalog.

    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/peter/sites/ozone/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/peter/sites/ozone/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/peter/sites/ozone/sites/all/modules/ldap_integration/ldapdata.module on line 355.
    * warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/peter/sites/ozone/sites/all/modules/ldap_integration/ldapdata.module on line 355.
miglius’s picture

miglius commented
Status: Active » Postponed (maintainer needs more info)

something went wrong during the upgrade. Can you recheck the ldapauth and ldapdata settings? Is ldap user able to authenticate after the update?

ellen.davis’s picture

ellen.davis commented

I had the same problem on my site. I applied the fix at http://drupal.org/node/349248. This fixed the issue.

miglius’s picture

miglius commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.