Like the title says, adding a Field Collection field to my content type, even an empty one, causes the nodes of that content type to give 500 errors. As soon as I delete the Field Collection field, the node works again.

Also, when I delete the empty field collection field, I get the following error:

EntityFieldQueryException: Unknown field: field_slides in EntityFieldQuery->addFieldCondition() (line 767 of [path to theme]/includes/entity.inc).

Disabling all other third party modules doesn't solve this issue, and this is a relatively clean install. Actual version of module not available in dropdown, my Modules list says "7.x-1.0-beta3+4-dev."

Comments

thirdboxcar’s picture

thirdboxcar CreditAttribution: thirdboxcar commented
Version: 7.x-1.0-beta3 » 7.x-1.x-dev

Update: it was the dev version that was causing the issue. Apologies for the miscategorization. Rolling back to 7.x-1.0-beta3 solved my issue.

timgilmour’s picture

timgilmour CreditAttribution: timgilmour commented
Version: 7.x-1.x-dev » 7.x-1.0-beta4

I'm seeing this exact issue on 7.x-1.0-beta4 also. No nodes with a field collection, using the embedded widget, can display at all, due to 500s.

rteuber’s picture

rteuber CreditAttribution: rteuber commented

This is related to the i18 translation added in Beta4.

I had the same issue with Fields created after updating the module to last Beta. All fields created before worked fine, new fields draw Error 500.

Error message in error.log of server mentioned a call to i18 translation even i18 is not installed on my system.

Roll Back to Beta 3 solved the issue.

Hope that helps to fix the issue.

timgilmour’s picture

timgilmour CreditAttribution: timgilmour commented

Confirmed that reversion to beta3 takes care of the error. Now i guess the question is: is there a way to integrate the i18 support, and upgrade previous field definitions so that they are compatible with beta4? Or is it even worth it (it is a beta after all).

adam_b’s picture

adam_b CreditAttribution: adam_b commented

Confirming that with beta4, all field-collection fields caused a 500 error. Reverting to beta3 fixed it.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett commented
Status: Active » Postponed (maintainer needs more info)

Is this still reproducible with the dev version of Field Collection and Entity?

aldenjacobs’s picture

aldenjacobs CreditAttribution: aldenjacobs commented
Priority: Major » Normal
Status: Postponed (maintainer needs more info) » Fixed

This sent me for a huge loop the other day, but I worked through it with some basic troubleshooting, having run into similar issues updating modules with beta/alpha dependencies previously.

To my knowledge, this issue is no longer a problem, as long as you update your modules all the way up to current dev releases. If anyone has a run in with this, feel free to reopen and I'll walk through the steps I took to actually get the updates to work.

Basically, a good first couple o' steps is to remove all related problematic modules from your modules directory, clear caches, and uninstall modules in question, and then simply upload the latest dev release of Field Collections AS WELL AS Entity API. Of course run Update.php just to be safe!

Cheers!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.