Hi,

I just discovered this module and it looks great. To be honest, I have not been working with Views Attachments a lot in D6 so this might be a beginner question. I have been thinking about the distinct advantages and implications of using EVA. I watched the tutorial on drupalize.me and torontowebsitedeveloper.com and as always with Drupal, similar results to what was presented in those tutorials could be achieved in various ways, e.g.:
- I could create a block in views and place it on the user profile through block settings. The limitations here would be that it would not be possible to display the view easily between other content fields. Context module might offer additional advantages to decide when to display the block.
- If I use panels, I could create a pane and overwrite the user display and then place the published articles as part of a pane where I need them.

I noticed that some users have asked similar questions about views attachments vs. content panes before.

Maybe we could use this thread as a start of a documentation to point out some of the dis-/advantages of the various approaches, e.g.
- As the view is stored as a field, will it work with other contributed modules such as field permissions, field group etc.?
- What are the differences between EVA and panes?
- If I attach multiple views, can they all inherit exposed filters? Is that something that cannot be achieved with panes?

Thanks, J.

Comments

mkadin’s picture

mkadin commented

I haven't used panels extensively, so I can't speak to its advantages over content panes.

Also, EVA "Fields" aren't really fields. They appear on the 'manage display' tab, but they aren't a part of the field system. Thus, field permissions won't work for them. Field groups, however, will work just fine.

The big advantage of using EVA over a basic block is that you can pass in arguments from the entity the view is attached to as contextual filters. With a block, you could only do this from the URL.

You seem also to be confused (and its the naming of this module that is at fault) with the different between an EVA and an 'attachment' display type in views. Views has a built in 'attachment' display type, which allows you to stick a view before or after another view. An EVA is embedded on an entity, not a view.

jelo’s picture

jelo commented

Thanks for the quick reply. I thought I had read somewhere that EVA is going to be a replacement for the inbuilt views attachment displays. But now that I think about it, that doesn't make much sense...

finex’s picture

finex commented

And what about display suite fields which can be configured to obtain the same results of EVA?