Just tried to use Field Collection for a new content type.. I am not able to view any newly created content.. The error being logged is..

2012/04/15 18:09:37 [error] 26315#0: *22219 FastCGI sent in stderr: "PHP Fatal error:  Call to undefined function entity_i18n_string() in /home/websites/platform/sites/all/modules/contrib/field_collection/field_collection.module on line 913" while reading response header from upstream,

I have not tried the dev versions of Field Collection or EntityAPI modules because this is a production site and only uses stable/beta/release..

Comments

bmx269’s picture

bmx269 commented

I just received this same error.

Fatal error: Call to undefined function entity_i18n_string() in field_collection/field_collection.module on line 913

onegenius’s picture

onegenius commented

I have the same error also after updating my current version.

Macronomicus’s picture

Macronomicus commented

where did you find that error? Im getting WSOD on any node that has a field collection and no errors.

wipeout_dude’s picture

wipeout_dude commented
Title: Error on pages with field collection.. » WSOD on pages with field collection and undefined function error in logs..

You can find the error in your web server error logs or php error logs.. I am running nginx so its in /var/log/nginx/error.log..

Glad I am not he only one with the problem.. I'll update the title to indicate its a WSOD..

Routh’s picture

Routh commented

Confirming I had this error as well. Error only occurs with beta4. Rolling back to beta3 fixes the issue.

Macronomicus’s picture

Macronomicus commented

I upgraded to the dev and also upgraded to the most recent entity module, this got rid of the wsod's for me, I still have issues getting the operations to show in a collection view though.

broon’s picture

broon
Location Potsdam
commented

Confirming the error. Even with latest beta4 of field_collection and latest dev version of entity, I am still getting WSOD.
I am really hoping for both modules to get rather stable because field_collection is awesome and exactly what I need currently.

iamEAP’s picture

iamEAP commented
Priority: Normal » Major

Looks like Field Collection Beta4 references a function only introduced in a dev build of Entity released on the same day. Going to bump this up to major, as all sites using i18n String will have broken field collection pages.

iamEAP’s picture

iamEAP commented

Actually, if you check the release notes for Beta4, it specifically mentions the latest dev build for Entity API. Also see #1446674: make the interface translatable

I was going to move this to the Entity API queues, but I'm sure fago is already aware of the urgency, and it'd probably be better to keep it here so that others coming to this issue queue don't create a duplicate.

iamEAP’s picture

iamEAP commented

If you go ahead and use the dev of Field Entity, you absolutely must also upgrade your i18n to the latest dev or, once it's released, 7.x-1.5 (see #1530018: Create a new stable release 7.x-1.5). If you do not, your site white screens and drush starts segfaulting.

See also: #1518062: Latest DEV cause segmentation fault in drush

wipeout_dude’s picture

wipeout_dude commented

Thanks for the information iamEAP.

So I can get the job done I think I will roll back to beta3 as suggested by Routh until a new release of Entity is made.. I'll just have to ignore the messages telling me there are updates available until those updates include Entity.. :)

iamEAP’s picture

iamEAP commented
Status: Active » Needs review

Looks like both i18n and Entity API now have stable releases that correspond to Field Collection 7.x-1.0-beta4:

Entity API 7.x-1.0-rc2
i18n 7.x-1.5

You can upgrade all of the above and be fine.

bofrost’s picture

bofrost commented
Status: Needs review » Fixed

#12 works fine!
Updating Entity API should be enough... but it can't be bad to update i18n 7.x-1.5 as well.

Status: Fixed » Closed (fixed)

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