Closed (fixed)
Project:
EVA: Entity Views Attachment
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Feb 2012 at 15:16 UTC
Updated:
6 Jul 2012 at 01:33 UTC
Jump to comment: Most recent file
Comments
Comment #1
Fr0s7 commentedThere is a similar (possibly the same) bug related to caching.
After adding a new View display of type Entity Content and configuring it properly, the view does not appear in the content type as expected. When reviewing the Manage Display tab of the content type in question, the view still does not show up. However, if your click 'Save', the view now appears in the list and can be re-ordered properly. It's important to note that this needs to be done for every view mode (Default, Full content, Teaser, etc.) before the view will appear correctly.
Comment #2
rdickert commentedThanks bforchhammer!
This patch saved my bacon -- part of my site was breaking when I updated Views. For me this patch solved the problem in:
#1290350: EVA stopped displaying after upgrade to 7.x 1.1
Bumping priority to major in hopes that the maintainer will take a look at this and update the module - this is actually a critical issue to anyone using EVA who is updating from certain dev versions of Views 7.x-3.x that preceded the stable release.
Comment #3
mshepherd commentedIs this maybe related? #1531042: Cloning views that contain Entity content
Comment #4
Macronomicus commentedMy issue was the eva fields would not display any content, where they did before upgrading to recent views.
This module does not work without the given patch in the OP.... the patch works great!
Cheers!
Comment #5
vadym.kononenko commentedOnly after I've applied this patch I got my eva's views display as field on the "display fields" page.
Comment #6
mkadin commentedMakes sense to me. I can't seem to reproduce this error, but I believe this patch does the same thing - only lighter. There's no need to actually load all of the views and such...if you follow the rabit hole into views_load_all_views, eventually you get to ctools_export_load_object_reset(), which I think is what we need.
Can someone who is experiencing this problem test this patch to see if it clears it up?
Comment #7
bforchhammer commentedHm, not sure what's changed since February but I'm actually having a hard time reproducing this problem now myself...
Comment #8
bforchhammer commentedScrap that last comment. The problem still exists, and yes the patch in #6 also solves seems to solve the issue for me. Thank you!
Comment #9
bforchhammer commentedComment #10
mkadin commentedCommitted to the dev branch. Thanks folks. New release coming soon, just got git access to this module.