First off thanks for the module. It is great. I am using it successfully on other sites that don't use EVA.

Not sure if I would really say this is a bug with this module but it is not compatible with EVA: Entity Views Attachment.

When both enabled it causes an infinite loop and you get an error like: "PHP Fatal error: Maximum function nesting level of '500' reached, aborting! in ....../includes/cache.inc on line 335"

This is because 

function _extrafield_views_integration_get_extra_fields_for_entity_type($entity_type, $bundles, &$extra_fields) {
  foreach ($bundles as $bundle) {
    $temp_fields = field_info_extra_fields($entity_type, $bundle, 'display');

This function is called by extrafield_views_integration_views_data. When field_info_extra_fields is called it in turn calls eva_field_extra_fields which needs Views information so it comes back to extrafield_views_integration_views_data thus causing the infinite loop.

The only way around this that I can think of right off is making a custom version of field_info_extra_fields that would call all implementations of hook_field_extra_fields except eva_field_extra_fields. Though that feels kind of hacky.

I am not sure if is worth it but it would nice if there was some kind of notice on the project page that it is not compatible with EVA since it has over 25k usage.

Comments

dasRicardo’s picture

dasRicardo commented

First off, sorry for my lately answer. I take a look into the code and change a little bit so now you can use "EVA" and "Extrafield Views Integration" on the same installation without any problems. I made a new release so it can be download in a while.

Thanks for using and reporting.

Sorry for my english, i'm not a native speaker!

dasRicardo’s picture

dasRicardo commented
Issue summary: View changes
Status: Active » Closed (fixed)
tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Status: Closed (fixed) » Needs work

Re-opening this because it is not working with EVA again.

EVA hasn't been updated so it may be change in Views that caused this. I never was able to test the original fix.

I confirm this problem with a test site with only this module, EVA, Views and View UI module enabled.

The path for all the default Views that come with the Views module are broken. They list as '/' and if you edit them you get a lot of errors.

It would great if there was notice on the project page because tracking down that the Views problems I was having on my site took forever to figure out it was combination of these 2 modules. Others might also have this problem.

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Status: Needs work » Active

Changing to active because this isn't a current patch

Also

First off, sorry for my lately answer.

No problem I understand it is contrib module

Sorry for my english, i'm not a native speaker!

No problem at all. English seems good to me!

johnpitcairn’s picture

johnpitcairn commented

I have the same issue:.

With EVA module enabled (I need that for Commerce Backoffice Order), enabling this module breaks every view on the site.

Visiting any view's edit page displays the message: Display "Defaults" uses fields but there are none defined for it or all are excluded.

Disabling this module fixes all the broken views.

  • dasRicardo committed c0114b8 on 8.x-1.x 
    Issue #2085909 by das_ricardo: add static variable to prevent infinite...
dasRicardo’s picture

dasRicardo commented

Hello,

i will try to check if i can reproduce this and fix it hopefully.

dasRicardo’s picture

dasRicardo commented

OK, i set up a test site only with the modules from below and everything works as expected. Have created a simple content view and everything works like a charm (editing, show the view page). Maybe u have some more information for me?

  • drupal: 7.43
  • eva: 7.x-1.2
  • views: 7.x-3.13
  • views UI: 7.x-3.13
  • extrafield_views_integration: 7.x-1.3
sawtell’s picture

sawtell commented

Hi dasRicardo,

I have tried to recreate the issue with a vanilla install but like you I failed to expose the bug. However, working on a number of other websites this issue is still present.

From what I can tell, the issue occurs when defining the views field handlers.

_extrafield_views_integration_get_extra_fields_for_entity_type() is called during hook_views_data(), this in turn makes a call to field_info_extra_fields() which invokes all calls to hook_field_extra_fields(). It's during this that the conflict with eva occurs.

eva implements hook_field_extra_fields() in which it tries to load all the available views to use as the extra field displays, I believe this is what's causing the issue when hook_field_extra_fields() is invoked during hook_views_data().

attiks’s picture

attiks commented

Ran into the same problem, it works most of the time, but once in a while (maybe after cache clear) the eva field disappears. If I manually save the EVA view, the field appears again. The field disappears completely, it's not even visible anymore on the manage display page, so I suspect it's some kind of race condition.

arpas’s picture

arpas commented
Version: 7.x-1.2 » 7.x-1.3

When using Extrafield Views Integration with combination with EVA Features witch includes views are shown overridden after clear cache. This isn't mentioned in https://www.drupal.org/docs/7/modules/features/troubleshooting-reasons-f...

bohart’s picture

bohart
Location Lutsk, Ukraine
commented
Priority: Normal » Minor
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7.

All D7-related issues are marked as outdated in a bunch.
Still, everyone can apply the patch above to their projects.

If the issue's topic is actual in D10+ versions, please create a follow-up issue or comment on this one (to re-open and switch to the 2.2.x development branch).
Thanks!