Errors after upgrading to Beta7 [#2229857]

Hi,

I was finally able to upgrade from Beta4 this weekend after resolution to the error https://drupal.org/node/1877800

All seemed to work but today there are new issues starting to surface..

1) When saving new content with a field collection I get a WSOD..

2) A field collection field that is setup to have 5 items is only showing up with 4..

3) Any attempt to modify the field settings on the content type produces the error..
Attempt to update field Booking profile failed: Cannot add index <em class="placeholder">field_book_prof_revision_id</em> to table <em class="placeholder">field_data_field_book_prof</em>: index already exists..

Might have to attempt a roll back to beta4 but that will be a real PITA..

Any ideas?

Comments

Comment #1

jmuzz CreditAttribution: jmuzz commented 31 March 2014 at 17:18

Status:	Active	» Postponed (maintainer needs more info)
Issue tags:	-Field collection

#1 - Can you post the error message? This page should help you get it. https://drupal.org/node/158043

#2 - Haven't seen that. Any idea how to reproduce it?

#3 - #2141781: Existing index issue with revision_id index

Comment #2

wipeout_dude CreditAttribution: wipeout_dude commented 31 March 2014 at 17:52

Thanks for the quick reply..

Enabled php error reporting as per instructions..

#1 - When creating a new node the error that is reported is..
Fatal error: Call to a member function save() on a non-object in /var/www/dev/sites/all/modules/contrib/field_collection/field_collection.module on line 905

#2 - Seems to be related to the "Hide blank items" field setting removing the last item in a non-unlimited field but unfortunately can't change it because of the #3 error..

#3 - Tried the fix-field.drush fix from https://drupal.org/node/2141781 which allowed editing the field to remove "Hide blank items" which has effectively solved #2 (although it didn't work with table prefixes so had to be modified).. Not sure what other effect it will have though.. Not solved #1..

Comment #3

wipeout_dude CreditAttribution: wipeout_dude commented 31 March 2014 at 18:05

Status:

Postponed (maintainer needs more info)

» Active

Comment #4

wipeout_dude CreditAttribution: wipeout_dude commented 31 March 2014 at 20:25

Some additional information..

I pulled a fresh copy of the live site and started again..

I noticed that content types with a single field collection field saved.. The content type that has the issue has 4 field collection fields.. As a test I deleted three of them leaving just one and the node saved..

So it would appear that the issue is somehow related to more than one field collection field on a content type..