Upgrade to Beta1 results in "Integrity constraint violation: 1048 Column 'module' cannot be null"

Same problem here. I get this message when running database updates

The following updates returned messages

entity_translation module

Update #7002
Failed: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null: INSERT INTO {role_permission} (rid, permission, module) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 3 [:db_insert_placeholder_1] => edit node original values [:db_insert_placeholder_2] => ) en user_role_grant_permissions() (línea 3043 de /Applications/MAMP/htdocs/mysite-1.com/modules/user/user.module).

I'm seeing the same thing when trying to update from 7.x-1.0-alpha2 to 7.x-1.0-beta1 with both drush updb and /update.php.

• Drupal 7.16
• PHP 5.3.17
• MySQL 5.1.38

wft, let's try this one :(

Apply the patch and run the updates, you should be ok then.

@plach Applied patch, updated successfully. Let's wait several more reviews.

Patch applied cleanly and the updates ran (7002 - 7004), but when trying to load the site it white-screened.

Watchdog had the following error:

Exception: Cannot initialize entity translation path variables (invalid path scheme). in EntityTranslationDefaultHandler->initPathVariables() (line 1401 of /Users/garrettc/Work/sandbox/wdcs/sites/all/modules/I18n/entity_translation/includes/translation.handler.inc).

Clearing the cache failed with the same error. I rolled back to a previous version of the database that hadn't been touched by the pre-patched beta1 upgrade and it all updated okay. Perhaps some cruft got left in the database by the failed update? Something to watch out for anyway.

Site is back and the new UI work looks great.

Ok, I committed #3, a -dev snapshot will be out in some hours. You can safely use that one instead of beta1.

Feel free to reopen this if it does not work for you. I'll roll a new beta soon, but I'd like to wait and see whether new bad bugs come up so I'll wait for a while.

Just a note that I went from alpha2 to beta 1 (10 minutes ago) and get this error:

Exception: Cannot initialize entity translation path variables (invalid path scheme). in EntityTranslationDefaultHandler->initPathVariables() (line 1401 of /xxxxxxxxx/docroot/sites/all/modules/entity_translation/includes/translation.handler.inc).

I also tried the current 7.x-1.x-dev and got the same error.

Does clearing caches fix it?

Drush cc all and drupal_static_reset() neither helped. Didnt try the patch.

Guys if you are talking about the error in #7, please open a new issue. This is a mess right now.

Patch from #3 also fixed issue for me. Thanks plach!

- Disabled and deleted alpha2
- Downloaded and enabled latest dev
Seems to work with small testing and the errors are gone.

-Installed latest dev
-Cleared Cache
Seems to be working again. Thanks for the help.

I'm using the dev version and I am too having this issue.

The patch in #3 solves the question.

Tks.

#7 raised as http://drupal.org/node/1833496

I can confirm #3 worked for me (using alpha).

Thanks

Deleted alpha1 directory from /all/modules
drush dl entity_translation
drush updb

All ok so I think its a leftover of alpha1 that breaks beta1

Cheers

Installing the last dev version solved my problem.

Committed this follow-up: the quick fix above turned on workflow permissions by default, which is not what we want.

Any chances this fix gets soon applied to a stable version?

Right now the latest stable version is unusable without this patch.

Right now the latest stable version is unusable without this patch.

This is completely false, every new site can happily use beta1 :)
Moreover a new stable version would be more or less the current dev.

@plach I tried to install ET in a clean Drupal and I got this error. I had opened issue #1842178: Errors after enabling module for the very first time before finding this one.

When I said it was unusable is because beta1 is not being installed in a clean install.

You are right, sorry, I didn't realize this happens also on clean installations. I guess we need a new beta asap, then.

I get the same problem than posted initially by chefnelone. After a little debugging it seems to happens in the install file, in line 133 - 136. The permissions "edit [entity_type] original values" and "edit [entity_type] translation shared fields" is not known by the system yet (in the case of a new install), because it will be established in the hook_permission later on when the module file is called.
If someone can confirm this this observation, I would try to bring up a little patch for that.

This patch avoided the PDOException while enable/install the module at my host. Please try if it works for You.

This issue is already fixed in the latest dev...

You are right, thanks.

Beta2 is out :)

plach thanks for that.
You have been doing a great job!