Closed (duplicate)
Project:
EVA: Entity Views Attachment
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 May 2012 at 12:49 UTC
Updated:
11 Jul 2012 at 15:09 UTC
Comments
Comment #1
donquixote commentedfyi:
I already tried in page.tpl.php to render the main content, before I render the theme region with the EVA in it.
Does not help.
Comment #2
donquixote commentedOk, found why this happens.
See #1570716: EVA not showing up with ds_extras "Region to block" (ds queue) in the ds issue queue.
The problem is that EVA is a preprocess field.
I remember last time I discarded EVA was exactly for this reason: Preprocess fields are processed, even if they are not needed.
It would be preferable if it was just a ds field, imo.
Comment #3
mkadin commentedThe EVA code explains why it needs to use hook_entity_view_alter vs. hook_entity view (some core and contrib entities don't implement hook_entity_view). But Its my understanding that block theming occurs before either of those two functions. To get this working would be a significant change in eva's methodology for displaying the view...so I see this as more of a feature request.
Comment #4
donquixote commentedViews content panes (included in ctools, afaik) can be used to achieve results similar or equal to EVA, and they are not preprocess fields.
(organic groups ships with views configured as content panes)
They are just more difficult/confusing to configure than EVA, esp. in Display Suite (where they are "extra fields").
The ideal thing would be an EVA that is not in preprocess.
Comment #5
mkadin commentedI'm closing this for now as a duplicate of #1617030: Make EVA not be a preprocess field as that issue is more general.
I will cross post on that queue as well. I'm skeptical that this will be possible without major revisions, but given the popularity of DS it would be nice if it can be done.