Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Using the most current 'i18n 7.x-1.x-dev (2011-Feb-20)' on a basic Drupal7 test site, I get the following error on the frontpage when activating the submodule 'Multilingual Select':
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.language' in 'where clause': SELECT base.tid AS tid, base.vid AS vid, base.name AS name, base.description AS description, base.format AS format, base.weight AS weight, v.machine_name AS vocabulary_machine_name FROM {taxonomy_term_data} base INNER JOIN {taxonomy_vocabulary} v ON base.vid = v.vid WHERE (base.tid IN (:db_condition_placeholder_0)) AND (base.language IN (:db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => de [:db_condition_placeholder_2] => und ) in DrupalDefaultEntityController->load() (line 196 of /var/www/site_foo/includes/entity.inc).
After that nothing works any longer. The site is completely gone. Thanx for fixing!
Comments
Comment #1
Blooniverse CreditAttribution: Blooniverse commented... really strange, similarily as described in #1070580: 2 errors (undefined index, call_user_func_array) comment#2, this doesn't happen on my real Drupal development site with ~80 additional/optional modules!
Comment #2
Jose Reyero CreditAttribution: Jose Reyero commentedIf updating from an alpha version, you need to reinstall the module (or manually create the fields).
Comment #3
Blooniverse CreditAttribution: Blooniverse commentedThank you, Jose! I've upgraded now from dev to beta1 - things work quite fine now!!!
Comment #4
Jose Reyero CreditAttribution: Jose Reyero commentedComment #5
GStegemann CreditAttribution: GStegemann commentedI re-installed all the modules, but still get errors:
During installation of i18n_string the following error message is issued:
Shall I drop the table first? Or should the installation procedure check this?
Or when can I find the definition of the missing "base" columns?
Comment #6
Blooniverse CreditAttribution: Blooniverse commentedDear @GStegemann:
Please keep me/us informed about your progress!
Comment #7
GStegemann CreditAttribution: GStegemann commentedDear the_phi,
yes, I only disabled/enabled the module.
Following your suggestion I fully uninstalled the module. However, the table i18n_strings was not dropped by the system. Therefore I dropped the table manually. Then the re-installation went through w/o any errors.
There is may be one issue: everytime I enable another module a message is displayed that the string definition 'node:type:panel:description' was updated. Any ideas what is causing this?
Comment #8
enkara CreditAttribution: enkara commentedCould you please indicate which columns should be added manually? I can't uninstall the module, as I already have a lot of info I don't want to loose. If you could put the sql query would be really useful.
Here's what I've used, not sure if it's correct:
Thank you
Comment #9
GStegemann CreditAttribution: GStegemann commentedLooks fine to me so far. But as described in issue #1066886: Column not found: 1054 Unknown column 'base.i18n_tsid' in 'field list' the data type should be "INT UNSIGNED".
Comment #10
Jose Reyero CreditAttribution: Jose Reyero commentedGive a try to this. http://drupal.org/project/schema
Comment #11
Blooniverse CreditAttribution: Blooniverse commentedThank you for the hint, @Jose! I am, at the moment, comparing the output of Schema's SQL tab 'admin/structure/schema/sql' with phpMyAdmin's structure display!
Comment #12
Blooniverse CreditAttribution: Blooniverse commented... I've checked 'i18n' more or less thoroughly. It consists of the following main module and submodules:
In the Drupal database 'i18n' creates following independent tables (along with alterations of existing tables!):
My Advise:
If possible, uninstall/reinstall all of 'i18n'! This is the safest way. If not possible, respectively completely possible, procede with #1.
Below you find the affected SQL statements according to the output of 'admin/structure/schema/sql'.
My personal question concerning the db_table 'locales_target': Why is the field type not Boolean here? The comment makes me assume that it is!
Comment #13
Blooniverse CreditAttribution: Blooniverse commented... holy crap, where is this error (below) coming from now -- after saving a taxonomy/vocabulary term translation? It might seem like a taxo error, but I really don't think it is!
Probably I should file a new issue/bug report -- I have not seen anything similar to this!
Comment #15
Jerome F CreditAttribution: Jerome F commentedThe beta 3 update doesn't solve the problem does it ?
I can uninstall internationalisation menu but not the rest.
Although #12 is very detailed, I still don't know where to start after installing shema.
Comment #16
Blooniverse CreditAttribution: Blooniverse commented@Jerome F: Start at comment#12 in section 'My advice' !
This is not a bug -- this is a matter of the upgrade path procedure respectively a matter of the lacking upgrade paths (dev & alpha modules). The beta versions contain upgrade paths!
Comment #17
Blooniverse CreditAttribution: Blooniverse commentedComment #18
Blooniverse CreditAttribution: Blooniverse commented... reported comment#13 on #1095668: PDOException: SQLSTATE[23000]: Integrity constraint violation -- when saving taxo term translation !
Comment #20
dotnhack CreditAttribution: dotnhack commentedIt seems the beta4 doesn't fix that error I have installed Internationalization and Variable and JUST enable Variable and I have:
DatabaseSchemaObjectExistsException: Table cache_variable already exists. in DatabaseSchema->createTable() (line 630 of /var/www/vhosts/marioswine.com/httpdocs/includes/database/schema.inc).
The worst part is that I have installed it on my other site and it gave me an error but it works... Hope someone can help me.
Comment #21
andrea.corelli CreditAttribution: andrea.corelli commentedSorry guys, shouldn't this be fixed on beta's? I installed latest beta and it still won't add the missing fields.
Comment #22
70111m CreditAttribution: 70111m commentedsubscribe
Comment #23
m_wiking CreditAttribution: m_wiking commentedI have just tested this and I get this in the latest dev version
DatabaseSchemaObjectExistsException: Table i18n_string already exists. in DatabaseSchema->createTable() (line 629 of/var/www/mysite/includes/database/schema.inc).
Comment #24
my-family CreditAttribution: my-family commentedThe same problem also in 7.x-1.8 with i18n_block_language.
I had to uninstall the module and drop the table manually. But it is not possible on production site. So i think the issue is not fixed.
In addition, this problem breaks the block administration (after enabling Block languages, I was not able to edit and save any block, even without multilingual settings:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'i18n_mode' in 'field list': UPDATE {block} SET i18n_mode=:db_update_placeholder_0 WHERE (module = :db_condition_placeholder_0) AND (delta = :db_condition_placeholder_1) ; Array ( [:db_update_placeholder_0] => 0 [:db_condition_placeholder_0] => search [:db_condition_placeholder_1] => form ) ve funkci i18n_block_form_block_admin_configure_submit()
Comment #25
Jose Reyero CreditAttribution: Jose Reyero commentedSorry but if trying pre-release dev versions you need to be ready / capable for some manual table updates.
(And if not, we need to know exactly which upgrade path you've followed)
Comment #26
AdamGerthel CreditAttribution: AdamGerthel commentedI'm having the same problem as #24 using the released 7.x-1.8 (not dev). Activating Block i18n crashes the site completely:
Comment #27
kenorb CreditAttribution: kenorb commentedSee also: Unknown column 'base.i18n_tsid' when using Term Reference Tree module at SE.