error, WSOD & db corruption on install (PDOException: SQLSTATE[42000]: Syntax error or access violation: 1101 BLOB/TEXT...)

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1101 BLOB/TEXT column 'strings' can't have a default value: CREATE TABLE {icl_image_status} ( `id` INT unsigned NOT NULL auto_increment COMMENT 'The primary identifier for an image.', `data` LONGTEXT NOT NULL COMMENT 'Contains the image path of other data for embedded objects.', `type` VARCHAR(32) NOT NULL DEFAULT '' COMMENT 'The type of data.', `language` VARCHAR(12) NOT NULL DEFAULT '' COMMENT 'The language of this data.', `tnid` INT unsigned NOT NULL DEFAULT 0 COMMENT 'The translation set id for this data, which equals the data id of the source data in each set.', `md5` VARCHAR(32) NOT NULL DEFAULT 0 COMMENT 'md5 of the data contents', `strings` LONGTEXT NOT NULL DEFAULT '' COMMENT 'strings in the image/data that need translation.', PRIMARY KEY (`id`) ) ENGINE = InnoDB DEFAULT CHARACTER SET utf8 COMMENT 'The ICanLocalize image translation statuses. Also for...'; Array ( ) in db_create_table() (line 2657 of /var/www/includes/database/database.inc).

...and then WSOD! I think my db just died on me. Thank God this was a test installation.

...Yep, I need to reinstall. I disabled all contrib modules from the system table in my db -just in case it might work again- and still nothing.

subscribe
drupal 7.8 and last 7.x-1.x-dev version

Same happened to me...

I've removed a complete translation_management directory, and at least the WSOD gas gone... ;-)

I've faced many crashes due to different errors. It seems to me that many things were moved among some files, so the current -dev version (dated 2011-May-19) seems to be quite useless, as it is. I was not able to install (uninstall) it, or run cron after, and so on.

I've had to patch many files, and here (in the attachment) is everything I've done.

After that, I was able at least to install modules ('Core', 'Translate', 'Content', 'Google Translate' and 'Local Translation Service' in this order), and make my test installation to "survive" cron jobs (as it seems now...).

Hope it will help to someone else...

Forgot to mention that I've applied the patch from #1010166: Drupal 7 node hooks expect pass by value, not by reference as well, but haven't include it in my patch, to keep things as clear as possible...

Yeah, my site is toast. I was 99% finished building it.

I think this problem happens because mysql blob type field doesn't support a default value.

BLOB and TEXT columns cannot have DEFAULT values.

See some reference from mysql docs.

So if you have a field in hook_schema described as so:

      'script' => array(
        'type' => 'text',
        'size' => 'normal',
        'default' => '',
      ),

Removing 'default' array-item will fix this.

Another reference Webform issues: BLOB/TEXT column 'excluded_components' can't have a default value.

Taking out the default key helps, but the next problem that comes up is an error stating that "icl_content_status" already exists. This is because in D7 hook_schema is applied automatically when modules are enabled, and does not require drupal_install_schema() inside a hook_install(). see here:

function icl_content_install() {
  drupal_install_schema ( 'icl_content' );
  
  // Set module weight for it to run after core modules.
  db_query("UPDATE {system} SET weight = 100 WHERE name = 'icl_content' AND type = 'module'");
  
}

This looks like it was just a holdout during the d6->d7 conversion.. i'm not sure how it passed testing though since it woulda killed the site on install.

here's the patch that removes the default key & comments out the drupal_install_schema() lines.

Currently we're reimplementing this module from scratch in our codesprint:
http://drupalevents.ch/drupal/codesprint-2012

Thus all current bug reports and feature requests are dropped. Please recheck once the the sprint is completed.

After removing 'default' from any array item of text data type...
This this work great!

@miro_dietiker: I haven't re-visited this module for quite some time. What was the outcome of the codesprint after all? There haven't been any commits to this project for about 5 months now. Did the rewrite from scratch happen? If Translation Management Tool is meant to replace this project, can you please make it clear in the project's page. Thanx in advance.

I passed this module back to the maintainers as we decided not to work with this.
See a different issue like #1010166: Drupal 7 node hooks expect pass by value, not by reference with my last comment #17

Since i'm NOT maintainer for this project here, i cannot add any kind of statement on the project page. We (the codesprint participants) just did something completely different. It's up to the maintainers...
I'm sorry i can't help. But checkout tmgmt, it rocks!

Thanx for taking the time to explain Miro. That's understandable and fair enough.

PS: ...and sorry for the late reply - being summer and all :P