I'm just not sure why a separate module is needed for what can be achieved with a block view? Is there less overhead with this module?

Comments

mkadin’s picture

mkadin commented

1) eva can pass the entity's id or its properties and fields (via token) in to the view as arguments for contextual filters. How would you do this with a block?

2) if you have multiple entities being shown on a page, multiple eva views will appear as well.

3) you can put the eva view between fields within the entity's rendered display.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Status: Active » Postponed (maintainer needs more info)

...

coredumperror’s picture

coredumperror commented

When a feature of your site requires a node, but you want that "node" to actually be the results from a view, this module lets you define a content type that stores data in its fields which EVA then translates into arguments for the View. I've found this to be invaluable for multiple features on my site, especially with the extra hook I added that lets the parent node's view mode percolate down into the nodes returned by the view.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

...I believe we can safely close this one now ;)