Fail on installing dbee v7.x-3.0

Added log errors

What you mentioned:

1. disable the dbee module
2. uninstall the dbee module
3. update the dbee module files
4. enable the dbee module (and the update script should not be run)

Is exactly what I did, I didn't run the update script after changing the module code to the new version. After the crash the module is enabled in the database, but the user table is not altered with the new fields. Therefore the whole Drupal database is messed up and it becomes impossible to disable the module again, or even clear the cache. Everything keeps crashing with the error code

exception 'PDOException' with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'u.dbee_mail' in 'field list'' in                             [error]
/var/www/html/includes/database/database.inc:2227

I also tried to update the files and then run the update script, this also doesn't work for me with the same error message if I remember correctly.

I highly doubt we have emails that are longer as 254 since this is the current length of the table as well. So updating it to 500 shouldn't be an issue since it's an upscale instead of a downscale.

I don't think the issue are the indexes. But the schema alter

/**
 * Implements hook_schema_alter().
 *
 * Edit the mail and init field description precising they are encrypted, add
 * 2 new fields storing lowercase encrypted mail and init values.
 */
function dbee_schema_alter(&$schema) {
  if (isset($schema['users'])) {
    // Change the description on the {users} table fields.
    $schema['users']['fields']['mail']['description'] = "User's encrypted e-mail address.";
    // The encrypted value is a serialized data, the length must be bigger.
    $schema['users']['fields']['mail']['length'] = 500;
    $schema['users']['fields']['init']['description'] = 'Encrypted e-mail address used for initial account creation.';
    $schema['users']['fields']['init']['length'] = 500;

    // Create 2 new fields.
    $schema['users']['fields']['dbee_mail'] = array(
      'type' => 'varchar',
      'length' => 500,
      'not null' => TRUE,
      'default' => '',
      'description' => "User's encrypted lowercase email address.",
    );
    $schema['users']['fields']['dbee_init'] = array(
      'type' => 'varchar',
      'length' => 500,
      'not null' => TRUE,
      'default' => '',
      'description' => "Encrypted lowercase e-mail address used for initial account creation.",
    );
  }
}

According to the manual of MySQL 255 is the max length possible for a varchar. However I'll try the index fix you mentioned.

I'm working on a MySQL 5.6.32 database. Going to test the patch in a few minutes.

So I applied the patch and now the module enables fine. However the email addresses are not being encrypted upon enabling of the module. (I disabled, uninstalled, updated the code, applied the patch and then enabled the patched module.)

Going to the configuration screen of DBEE and clicking the save button with the checkbox "re-encrypt" users encrypted everything. Tested and logging in with emails works without an issue.

If the emails need to be encrypted upon enabling of the module you'll need to add the same logic as in the "hook_enable" code.

   drupal_set_message(t('DataBase Email Encryption module enabled'));

  // Encrypt all existing email addresses.
  module_load_include('inc', 'dbee', 'includes/dbee.users');
  dbee_update_crypt_all('encrypt');

But add this in the install hook. Currently the dbee_update_crypt_all is only triggered by the dbee update hook (7300)

Uploaded a new patch where I moved the encrypt code to the install hook and fixed some typos. Since the update hook calls the install hook, there should be no issue with the code move.

I also just came to the same conclusion that the crypt_all function should not be moved. I tested patch #12 and it's working fine. However emails are not being encrypted right after the install, an extra save is needed on the configuration form.

I confirm the patch is working and all users are correctly encrypted upon enabling the module from Drush. Patch looks good!

@thedut Thanks for your effort and quick responses, glad we fixed it so fast! Now we can get rid of AES ;)