I tried to update Entity Translation from beta3 to beta4. Beta3 version works fine but after updating to the latest version I get the following errors:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision_id' in 'field list': INSERT INTO {entity_translation} (entity_type, entity_id, revision_id, language, source, uid, status, translate, created, changed) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9), (:db_insert_placeholder_10, :db_insert_placeholder_11, :db_insert_placeholder_12, :db_insert_placeholder_13, :db_insert_placeholder_14, :db_insert_placeholder_15, :db_insert_placeholder_16, :db_insert_placeholder_17, :db_insert_placeholder_18, :db_insert_placeholder_19); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 88 [:db_insert_placeholder_2] => 88 [:db_insert_placeholder_3] => de [:db_insert_placeholder_4] => [:db_insert_placeholder_5] => 34 [:db_insert_placeholder_6] => 1 [:db_insert_placeholder_7] => 0 [:db_insert_placeholder_8] => 1424283755 [:db_insert_placeholder_9] => 1432551974 [:db_insert_placeholder_10] => node [:db_insert_placeholder_11] => 88 [:db_insert_placeholder_12] => 88 [:db_insert_placeholder_13] => en [:db_insert_placeholder_14] => de [:db_insert_placeholder_15] => 34 [:db_insert_placeholder_16] => 1 [:db_insert_placeholder_17] => 0 [:db_insert_placeholder_18] => 1424885156 [:db_insert_placeholder_19] => 1432559576 ) in EntityTranslationDefaultHandler->doSaveTranslations() (line 611 of //sandbox/sites/all/modules/entity_translation/includes/translation.handler.inc).

I am no skilled coder but it looks like a bug to me. Could you have a look at this, please? Thanks.

Comments

Samvel’s picture

Have same issue

Samvel’s picture

Status: Active » Closed (works as designed)

Sorry, it was not runned database updates.
So i think that this is not bug

pranavpathak’s picture

Hi,

In case someone is also facing this issue then please run below command in drush.

drush updb

In short we need to run database udpate .

Thanks,
Pranav