Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I just updated to beta7 and an error occurs when i activate a feature from features module which saves a nodetype configuration with field collections.
On activating i get the following Error:
DatabaseSchemaObjectExistsException: Cannot add index field_element_revision_id to table field_data_field_element: index already exists. in DatabaseSchema_mysql->addIndex() (line 437 of /Users/huche/Sites/van/includes/database/mysql/schema.inc).
It seems as if it is raised when calling field_collection_field_schema()
The hook is invoked in field core modules field_update_field($field).
Any Suggestions?
Comments
Comment #1
Chris Burge CreditAttribution: Chris Burge commentedI ran into the same issue this morning when attempting to update a feature. The following commit is probably responsible: http://drupalcode.org/project/field_collection.git/commit/0fd332e7ce5fdd...
Unfortunately, I can't just rollback the module to 7.x-1.0-beta5 because there are two schema changes in 7.x-1.0-beta7.
Comment #2
Chris Burge CreditAttribution: Chris Burge commentedThis isn't an issue on which I can contribute much in the way of solving.
In the end, I downgraded to 7.x-1.0-dev (revision da9c22972048602a5d0324b9bd66c5907863baa1). This is the last commit before this bug appeared. Next, I manually removed the schema changes from my database. Finally, I changed the schema version in the system table for the field_collection module to 7003.
Comment #3
Chris Burge CreditAttribution: Chris Burge commentedSetting issue priority to Major because this bug breaks deployment.
Comment #4
bkonetzny CreditAttribution: bkonetzny commentedComment #5
alcroito CreditAttribution: alcroito commentedConfirming, I have the same issue.
The #27 patch at https://drupal.org/node/2141781#comment-8677137 fixes the issue, and it was committed to the field collection dev.
Comment #6
keopxWorked for me and this issue is duplicate.
The #27 patch at https://drupal.org/node/2141781#comment-8677137 fixes the issue, and it was committed to the field collection dev.