Posted by martink on December 9, 2008 at 4:43pm
| Project: | LDAP integration |
| Version: | 6.x-1.0-alpha2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
I just upgraded to Drupal 6.6, which meant upgrading from ldapauth 5.x-1.3 to 6.x-1.0-alpha2. I have all three modules installed (though actually I think I only need the authorisation).
Everything went ok apparently. I reinstalled the module and ran update.php which told me there were no new versions to upgrade to. However, when I logged in for the first time with an LDAP authenticated user I get this message:
user warning: Unknown column 'ldapgroups_in_dn' in 'field list' query: SELECT ldapgroups_in_dn, ldapgroups_in_attr, ldapgroups_as_entries, ldapgroups_dn_attribute, ldapgroups_attr, ldapgroups_entries, ldapgroups_entries_attribute FROM ldapauth WHERE sid = 1 in /var/www/drupal-6.6/sites/all/modules/ldap_integration/ldapgroups.module on line 150.Disconnecting ldapgroups made the issue go away
Comments
#1
It looks that for your installation there is something wrong in the ldapgroups database fields. Try disabling (and uninstalling) ldap groups module, then reinstalling it again. Installation should create a proper table fields.
#2
I tried uninstalling LDAP groups and go this:
* user warning: Can't DROP 'ldapgroups_in_dn'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_in_dn in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.* user warning: Can't DROP 'ldapgroups_in_dn_desc'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_in_dn_desc in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_dn_attribute'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_dn_attribute in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_attr'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_attr in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_in_attr'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_in_attr in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_as_entries'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_as_entries in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_entries'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_entries in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
* user warning: Can't DROP 'ldapgroups_entries_attribute'; check that column/key exists query: ALTER TABLE ldapauth DROP ldapgroups_entries_attribute in /var/www/drupal-6.6/includes/database.mysql-common.inc on line 322.
However, the reinstallation does seem to have done the trick!
#3
Had the same problem with ldap groups when migrating from 5.16 to 6.14. Disabled the data and group modules, tried uninstalling two modules, got the error message, re-enabled the two data and group modules (they were still listed on the modules page), and I was able to configure both ldap groups and data modules.
#4
In my case the reinstallation didn't work (it was an upgrade from D5 to D6). So I made a clean installation of drupal6, installed the ldap_integration module and took the table configuration. Then I dropped the old one and substitute it wih the new one and it works. In attachment there is the sql code.
#5
This problem is specific to the ldapgroups module. The upgrade code doesn't properly update the database schema, but the install code does. Uninstalling and reinstalling works because it completely destroys and rebuilds the ldapauth table. I found it rather frustrating that the update said it completed successfully, when in fact the module was not usable in the state it was left after the update. I have submitted a patch that properly updates the database schema and carries forward your settings here: #1021892: Upgrade from 5 to 6 does not work properly I am marking this issue as closed (duplicate) so the conversation can continue regarding the patch.