Field collection Beta4 -> Beta5 upgrade fails.

I can confirm I also experienced this when running updates for Entity API and Field Collection.

At the moment we've rolled back to Entity API 7.x-1.0-rc3 and Field Collection 7.x-1.0-beta4

Always back up your db's before updating!

I was having upgrade issues as well, usually complaining that the "field_collection_item_revision" table already exists (this was due to rolling back using Backup/Migrate, which does not delete extraneous tables)

So I manually deleted the "field_collection_item_revision" table, and then the beta4 -> beta5 upgrade proceded smoothly.

For anyone finding this thread I have managed to successfully roll back to Beta4 using the following procedure..

1. Copy the Beta4 module code back to sites/all/modules (or wherever your field_collection folder is)
2. Delete the "field_collection_item_revision" table.
3. In the "field_collection_item" table delete the "revision_id" and "archived" fields.
4. In your field collection field tables delete the "_revision_id" fields. (mine was only present on the first field collection field but check them all in case)
5. Clear all caches.

You should now be back to a working system on beta4..

Same problem here:
PDOException : SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'field_x_revision_id' cannot be null: UPDATE {field_data_field_x} SET field_x_revision_id=field_x_value; Array ( ) in field_collection_update_7001() (ligne 188 in /.../drupal/sites/all/modules/field_collection/field_collection.install).
I went back to beta4 with no problem, any ideas to fix that?

also, when i successfully ran update this morning i got a pile of these msgs:

Deleted 0 orphaned field collection items.
Deleted 3 orphaned field collection items.
Deleted 0 orphaned field collection items.
Deleted 0 orphaned field collection items.

and no other errors, msgs or warnings of any type

Hi! I used your advice #6 to return to Beta 4, followed step by step but I am getting a ton of errors now!
When I try to delete/add/modify a field collection item I get this:

PDOException: SQLSTATE[HY000]: General error: 1364 Field 'field_weekly_checklist_revision_id' doesn't have a default value: INSERT INTO {field_data_field_weekly_checklist} (entity_type, entity_id, revision_id, bundle, delta, language, field_weekly_checklist_value) 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, :db_insert_placeholder_20), (:db_insert_placeholder_21, :db_insert_placeholder_22, :db_insert_placeholder_23, :db_insert_placeholder_24, :db_insert_placeholder_25, :db_insert_placeholder_26, :db_insert_placeholder_27), (:db_insert_placeholder_28, :db_insert_placeholder_29, :db_insert_placeholder_30, :db_insert_placeholder_31, :db_insert_placeholder_32, :db_insert_placeholder_33, :db_insert_placeholder_34), (:db_insert_placeholder_35, :db_insert_placeholder_36, :db_insert_placeholder_37, :db_insert_placeholder_38, :db_insert_placeholder_39, :db_insert_placeholder_40, :db_insert_placeholder_41), (:db_insert_placeholder_42, :db_insert_placeholder_43, :db_insert_placeholder_44, :db_insert_placeholder_45, :db_insert_placeholder_46, :db_insert_placeholder_47, :db_insert_placeholder_48); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 8 [:db_insert_placeholder_2] => 243 [:db_insert_placeholder_3] => circle [:db_insert_placeholder_4] => 0 [:db_insert_placeholder_5] => und [:db_insert_placeholder_6] => 58 [:db_insert_placeholder_7] => node [:db_insert_placeholder_8] => 8 [:db_insert_placeholder_9] => 243 [:db_insert_placeholder_10] => circle [:db_insert_placeholder_11] => 1 [:db_insert_placeholder_12] => und [:db_insert_placeholder_13] => 59 [:db_insert_placeholder_14] => node [:db_insert_placeholder_15] => 8 [:db_insert_placeholder_16] => 243 [:db_insert_placeholder_17] => circle [:db_insert_placeholder_18] => 2 [:db_insert_placeholder_19] => und [:db_insert_placeholder_20] => 61 [:db_insert_placeholder_21] => node [:db_insert_placeholder_22] => 8 [:db_insert_placeholder_23] => 243 [:db_insert_placeholder_24] => circle [:db_insert_placeholder_25] => 3 [:db_insert_placeholder_26] => und [:db_insert_placeholder_27] => 62 [:db_insert_placeholder_28] => node [:db_insert_placeholder_29] => 8 [:db_insert_placeholder_30] => 243 [:db_insert_placeholder_31] => circle [:db_insert_placeholder_32] => 4 [:db_insert_placeholder_33] => und [:db_insert_placeholder_34] => 63 [:db_insert_placeholder_35] => node [:db_insert_placeholder_36] => 8 [:db_insert_placeholder_37] => 243 [:db_insert_placeholder_38] => circle [:db_insert_placeholder_39] => 5 [:db_insert_placeholder_40] => und [:db_insert_placeholder_41] => 64 [:db_insert_placeholder_42] => node [:db_insert_placeholder_43] => 8 [:db_insert_placeholder_44] => 243 [:db_insert_placeholder_45] => circle [:db_insert_placeholder_46] => 6 [:db_insert_placeholder_47] => und [:db_insert_placeholder_48] => 65 ) in field_sql_storage_field_storage_write() (line 448 of /srv/bindings/e49d00280243440ba70fa2bf8e2e6208/code/modules/field/modules/field_sql_storage/field_sql_storage.module).

Hi and thank you for your help. I went ahead and deleted the column from that table. I refreshed the caches and still have the same error appear. Any ideas? Tank you so much.

Someone?

This update made several sites unusable for several people.
This thread and this other thread: http://drupal.org/node/1876624
show this.

Please, can we be provided with either a patch or at least full instructions to roll back to beta 4?

I tried tht with no luck.

Thanks!

Federico

Thank you so much Kevin.

In order to make the revision_id field in the FC entities nullable, I used the following SQL query:
ALTER TABLE `pantheon`.`field_data_field_weekly_checklist` MODIFY `revision_id` varchar(20) NULL;
Is that correct? it worked for me (now I can save NULL values in the revision_id column).
I tried with a few of my FC entities (i have dozens and dozens of them on my site) but the error keeps
coming up when deleting/editing/saving FC entities.

About the revision fields, I deleted them completely (drop table). That was part of the instructions of
http://drupal.org/node/1877800#comment-6900826

So I cannot make them null.

Do you think that if I fill ALL revision_id columns from all FC entities tables with null value then the error would stop?

I wonder, was the revision_id column inserted by the Beta 5 version? if yes, wouldn't it be a good idea to DROP that
column as well?

It is so bad nobody is responding about how to either roll back "professionally" or a patch to repair whatever it is that Beta 5 did.

My site is basically broken and have been since early January when I updated...

Best,
Federico

Hi Kevin, thank you so much for your prompt response.

For one thing that software is for Mac and I'm using PC.

I have a GUI (MySQL Workbench) but it doesn't seem to have a way to make columns null-enabled other than with a query.

I don't quite understand what you mean by "data" and "revision" tables.

This table "field_collection_item_revision" I dropped/deleted and I cannot imagine a way of recovering it, since I even tried re-installing Beta 5 (which should add the new revision tables) and for some reason it didn't work.

From the table "field_collection_item" I dropped/deleted both the "archived" and "revision_id" columns.

Then I have all the data tables like "field_data_field_weekly_checklist".
From those tables (I have a lot because there is one per FC entity) I deleted/dropped the field_xxx_revision_id" column (in this case "field_weekly_checklist_revision_id").

The only thing left is a revision_id column, that I now am making null-able and then filling with null value.

Is this what you meant to do?

Best and thank you,
Federico

Kevinquillen "You can't just delete the tables, that will cause even more problems."

That's the opposite of what wipeout_dude recommended here:

2. Delete the "field_collection_item_revision" table.
3. In the "field_collection_item" table delete the "revision_id" and "archived" fields.
4. In your field collection field tables delete the "_revision_id" fields.

Additionally I'm lost when you say

I did not revert from beta5 to beta4.

As I understood, Beta 5 requires those tables (revision id) to actually have information because beta 5 does create revisions for FC entities; rolling back to beta 4 (what wipeout_dude was suggesting) seemed to be the only way for Field Collection to work regardless of the content of the revision_id columns (this, in theory; in my experience, both ways -either version of Field Collection- gives me error at this point.)

I installed heidisql, great piece of software. thank you.

How should I proceed? This is really killing me, this is work for a company and FC has been crazy since the update.

I wish the actual moderator/person in charge of the module would help us!

What do you recommend Kevin? updating again to Beta 5?

How do I recover the tables that wipeout_dude suggested to delete?

Best and thank you,
Federico

Not sure of the 'accepted' procedure, but to address the error that is on the screen, those fields have to allow for null values. That is how I got around it.

The fields that are throwing up the error need to be allow to have NULL. I am not sure if that was the intent of beta5 changes, but I got around it that way.

Hey guys,

I broke my site following your instructions :(

Here's the recapitulation:

• So I started with a greatly working site using FC beta 4.
• When I updated to beta 5 I found I couldn't save, edit, or delete -reported here- (sometimes it would work, but erratically - like taking 5 minutes to delete, then showing that it didn't delete the field, but later the field not being there in later renderings, etc).
• Then I follow #6 to roll back to Beta 4. That didn't work and the following error #12 started to appear IN ADDITION to the slow/interminable time for delete/edit/create and the randomness of the result of such operations (including sometimes creating multiple fields with the same name or deleting many too).
• After that, I've tried to update to Beta 5 again, since logically that would undo the changes suggested in #6 and re-generate the revision tables (I would be again on square 1); not so fast - the update this time around presented the error listed in #23.
• After the install/update I checked the sql tables to prove it hasn't changed and indeed - the update of Beta 5 did not add the revision tables.
• Now I am left in the situation that neither the Beta 4 (rolling back) nor the Beta 5 work at all, Beta 4 god knows why, Beta 5 since the tables it requires (revision) have been deleted by me (following #6) and the update is not adding them again.
• I have no way out!
• I would uninstall the whole module and wipe the field_collection table in a blink of an eye if it wasn't because my site has a structure of literally dozens of nested field collections and the structure is SO complex that thinking in re-doing it makes me want to trow up :(
• However the content itself is not at all important - since the site is in development so all the dozen-field collection items have in them is either nothing or random characters I wrote in order to test.
• Is there any way of starting the whole install again (of field collections beta 4) without losing the structure? with structure meaning, the actual nested field collections?
• Kevin's advice sounds great but it begins with the assumption that I haven't deleted tables, which I did (and quite a bit) following #6 so his advice doesn't apply to me any more - it seems.

Please folks (and specially the responsible for this module), work on this!!!

Best and thank you,
Federico

To revert back to beta4 on my local dev, I simply restored a backup and migrate backup for the DB and replaced beta 5 with beta 4 via git. I'm no longer getting a WSOD. I am not sure what I am missing but it seems ok now. I think it was trivial here as it didn't matter if I lost any other data as it's just a local dev.

Here's a patch for the wonky update function. It aims to cope gracefully with broken databases where you've run the failing update function already, but I can't guarantee any success if you've already tried any of the manual fixes suggested above.

Seems to work for me so far. The update completes, and I've been able to create new field collection items.

Here it is.

Federico, first thing to try is to edit the field_collection row in your database's 'system' table so the value of the 'schema_version' field is 7000. Then when you run update.php (or `drush updb`) it will re-apply update 7001 and later, creating the missing table/fields. Make sure you've applied my patch from #32 first.

Dear Matthew, I finally made it work by deleting manually every instance of the field_xxx_revision_id field and then running the update.php, with the patch already installed of course and by adding 7000 to the schema field.

The update this time went through perfectly.

However, I am at the same place I begun!

When I add or try to delete a field in a field collection drupal keeps "waiting" and doesn't go anywhere.
When back into the page, it sometimes didn't do anything, and most of the time created multiple versions (and keep creating them!) of the field.

In other words, it is as erratic as it was the first time I updated to Beta 5. I don't see any change made by the patch you submitted.

Please tell me how to proceed.

Thanks,
Federico

Here is a utility function I used to fix this

Hope that helps.

Note this makes non-restorable changes to your database - please backup first.

#32 worked perfectly for me as well. Thank you very much, Matthew Davidson!

Applying #32 patch , works fine for me , starting from Beta4 version Database

I can confirm that there is a way out both if you are coming from beta4 and if you come from beta 5, with or without updates.

Running all updates up to 7003 was important for me to ensure all fields in db tables are there.

Also verifying that all fields that say whatever_revision_id in the field collection data and revision fields are set to NULL and tick that box in phpmyadmin, if thats allow null?

run updates, clear cache, that should be it

could even switch between beta 4 and 5 code no problem after that

Patch #32 worked for me as well. Matthew, thanks very much for taking the time to create something that would help us clean things up after the initial upgrade issues.