The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.When configuring a field in the new content_taxonomy field. On submit I recieve this error:
user warning: Data too long for column 'name' at row 1 query: INSERT INTO variable (name, value) VALUES ('hs_config_content-taxonomy-field_where_in_the_world_0', 'a:7:{s:9:\"config_id\";s:43:\"content-taxonomy-field_where_in_the_world_0\";s:12:\"save_lineage\";i:1;s:15:\"enforce_deepest\";s:1:\"0\";s:10:\"node_count\";s:1:\"0\";s:12:\"level_labels\";a:2:{s:6:\"status\";i:1;s:6:\"labels\";a:1:{i:0;s:7:\"Country\";}}s:7:\"dropbox\";a:3:{s:6:\"status\";i:0;s:5:\"title\";s:0:\"\";s:5:\"limit\";s:1:\"0\";}s:11:\"editability\";a:4:{s:6:\"status\";i:1;s:10:\"item_types\";a:1:{i:0;s:7:\"country\";}s:16:\"allow_new_levels\";i:1;s:10:\"max_levels\";s:1:\"3\";}}') in C:\WeeWelcome\htdocs\includes\database.mysql.inc on line 172.
Comments
Comment #1
wim leersUGH! I had already shortened the prefix (from 'hierarchical_select_config' to 'hs_config') but obviously that was not enough. I think I'll have to create a dedicated table then, to support this without altering the variable table's schema.
A quick temporary solution is to make the field's name shorter.
Comment #2
32940stf commentedFor now I have widened the field in my dev environment (changing the field name would impact my search engine). I will wait until this issue is addressed.
Comment #3
wim leersI'm working on this now.
Comment #4
wim leersI asked in IRC and my suspicion is confirmed: I can just alter the variable table to make the "name" field 128 in size. This will NOT break upgrades to Drupal 6 (Drupal 6 has a default size of 128).
Comment #5
wim leersFixed.
Please make sure to run update.php!
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.