Error while viewing nodes with field collections when eva module enabled

I've the same problem using Drupal 7.9. Have you find any solution?
It would help me too....

I couldn't track it down in field collection, moving to EVA for now.

looks like the code is incorrect on line 148 of eva.module

Notice that the variable $entity is never defined within the function, so return $entity don't seem to make sense here.

if (!empty($build['#entity'])) {
    return $entity; // line 148
 }

And after changing the line to return $build['#entity']; it works.

if (!empty($build['#entity'])) {
    return $build['#entity']; // line 148
 }

can someone verify my solution and make this as a patch?

looks like #5 worked for me, still reviewing - thanks ken!

I was just about to post this problem and fix in #5 but I see it won't be necessary. #5 fixed by Drupal commerce site that Im filling with an ubercart migration.

Any plans to release this patch?

patch #5 worked for me as well,
would be nice to commit it to dev.

kenyangzj, thank you!

#5 is not a patch that can be committed, can someone create one?
See http://drupal.org/patch/create

I see the author is add the code of #5 to the dev branch.

Current, using the dev version will fix this problem.

This was fixed in #1278742-5: Notice: Undefined variable: entity and EntityMalformedException, commit http://drupalcode.org/project/eva.git/commitdiff/77069a9e

That was 6 months ago.

Actually, let's leave this open, since this fix was the ONLY thing committed after 7.x-1.1, and there could probably be a 7.x-1.2 just to prevent more issues from being filed.

2011-Sep-20 dev version (with this committed) fixes this problem for me.

To the maintainer: hey, how about a release with this fix?

I'm getting this error to trying to upgrade to the latest version too:

Undefined variable: entity in _eva_extract_entity_from_build()

PS Noobee (only 2 years lol) question is how to I upgrade to the 7.x-1.x-dev version? When I try I get the message that EVA is already installed. I have multiple, nested dependencies of EVA so I would have to uninstall the whole lot which isn't really feasible. I have backups so I guess I could roll-back and skip the EVA 7.x-1.1 version and go straight for the dev version?

The problem site/set-up here is an Omage/delta/context/Commerce build that uses EVA and Features.

The dev and 1.1 versions are close enough that you don't need to really uninstall anything. Simply delete the eva module directory and replace it with the dev files.

Ah. Thanks mkadin. I didn't know you could do that. Much appreciated.

I agree with the sentiments to release 7.x-1.2 with the fix for this.

Having just spent a good bit of time/frustration and finally tracking the issue to EVA, I was about to file an issue on this, as it breaks numerous places/modules on my site. I haven't even used EVA yet, I just had it installed because I intended to use it later.

I can confirm that the latest dev build fixed this error in the places I was seeing it.

This was fixed 10 months ago, please post a stable release to avoid this for others.

I understand your frustration. This module has been essentially unmaintinaed for a good while, and I just recently became its maintainer. With so many sites using the module, I want to get a lot of testing in on the dev branch before releasing a new 1.2 release. If you feel so strongly about a new release, please help me and other EVA users by testing out some of the patches in 'needs review' and trying out the dev release and looking for bugs. A new release is coming soon, but I need everyone's help to make sure the release is stable enough for the 8000+ EVA installations.

The current dev code is infinitely more stable than the current release. The 7.x-1.2 should be tagged now, and the new patches can go into 7.x-1.3.

As a maintainer of many modules that get bogus bug reports because of this specific issue, please wait no longer.

Tim seems confident in the changes :) New release has been set up.