You are here

Home » API reference » EVA: Entity Views Attachment 8.2

README.txt in EVA: Entity Views Attachment 8.2

Same filename in this branch
  1. 8.2 README.txt
  2. 8.2 tests/eva_docker/README.txt
Same filename and directory in other branches
  1. 8 README.txt
  2. 7 README.txt
ABOUT

"Eva" is short for "Entity Views Attachment;" it provides a Views display
plugin that allows the output of a View to be attached to the content of any
Drupal entity. The body of a node or comment, the profile of a user account,
or the listing page for a Taxonomy term are all examples of entity content.

The placement of the view in the entity's content can be reordered on the
"Field Display" administration page for that entity, like other fields added
using the Field UI module.

In addition, the unique ID of the entity the view is attached to -- as well as
any tokens generated from that entity -- can be passed in as arguments to the
view. For example, you might make a View that displays posts with an 'Author
ID' argument, then use Eva to attach the view to the User entity type. When a
user profile is displayed, the User's ID will be passed in as the argument to
the view magically.

That's right: magically.

Eva is powered by witchcraft.

HISTORY

Eva was originally developed by Jeff Eaton but never released. Larry Garfield
later cleaned it up and added the CCK integration, then released it under the
name 'Views Attach.' Endless confusion followed, as everyone thought it would
allow them to attach things to Views. Then Jeff Eaton refactored it for Drupal
7. Then they renamed it again, because they didn't want to write an upgrade
path.

Why *isn't* there an upgrade path? This version is built on top of Drupal 7's
Entity API as a single unified Views Display, while the D6 version juggled
NodeAPI and hook_user. While there's definitely feature parity, enough has
changed that cleanly upgrading a view from Views Attach 6.x-2.0 is essentially
impossible. They feel bad about it, and would accept patches that implemented
a well-tested upgrade path, but don't have the bandwidth to implement it
ourselves.

REQUIREMENTS

- Drupal 8

AUTHOR AND CREDIT

Original development: Jeff Eaton "eaton" (http://drupal.org/user/16496)

Actual D6 release, and version 2.0: Larry Garfield "Crell"
(http://drupal.org/user/26398)

D7 port and tomfoolery: Jeff Eaton "eaton" (http://drupal.org/user/16496)

D8 port started by Mike Kadin "mkadin" (https://www.drupal.org/u/mkadin) and
rounded out by Andy Hebrank "ahebrank" (https://www.drupal.org/u/ahebrank).

File

README.txt
View source 
  1. ABOUT

  2. 

  3. "Eva" is short for "Entity Views Attachment;" it provides a Views display

  4. plugin that allows the output of a View to be attached to the content of any

  5. Drupal entity. The body of a node or comment, the profile of a user account,

  6. or the listing page for a Taxonomy term are all examples of entity content.

  7. 

  8. The placement of the view in the entity's content can be reordered on the

  9. "Field Display" administration page for that entity, like other fields added

  10. using the Field UI module.

  11. 

  12. In addition, the unique ID of the entity the view is attached to -- as well as

  13. any tokens generated from that entity -- can be passed in as arguments to the

  14. view. For example, you might make a View that displays posts with an 'Author

  15. ID' argument, then use Eva to attach the view to the User entity type. When a

  16. user profile is displayed, the User's ID will be passed in as the argument to

  17. the view magically.

  18. 

  19. That's right: magically.

  20. 

  21. Eva is powered by witchcraft.

  22. 

  23. HISTORY

  24. 

  25. Eva was originally developed by Jeff Eaton but never released. Larry Garfield

  26. later cleaned it up and added the CCK integration, then released it under the

  27. name 'Views Attach.' Endless confusion followed, as everyone thought it would

  28. allow them to attach things to Views. Then Jeff Eaton refactored it for Drupal

  29. 7. Then they renamed it again, because they didn't want to write an upgrade

  30. path.

  31. 

  32. Why *isn't* there an upgrade path? This version is built on top of Drupal 7's

  33. Entity API as a single unified Views Display, while the D6 version juggled

  34. NodeAPI and hook_user. While there's definitely feature parity, enough has

  35. changed that cleanly upgrading a view from Views Attach 6.x-2.0 is essentially

  36. impossible. They feel bad about it, and would accept patches that implemented

  37. a well-tested upgrade path, but don't have the bandwidth to implement it

  38. ourselves.

  39. 

  40. REQUIREMENTS

  41. 

  42. - Drupal 8

  43. 

  44. AUTHOR AND CREDIT

  45. 

  46. Original development: Jeff Eaton "eaton" (http://drupal.org/user/16496)

  47. 

  48. Actual D6 release, and version 2.0: Larry Garfield "Crell"

  49. (http://drupal.org/user/26398)

  50. 

  51. D7 port and tomfoolery: Jeff Eaton "eaton" (http://drupal.org/user/16496)

  52. 

  53. D8 port started by Mike Kadin "mkadin" (https://www.drupal.org/u/mkadin) and

  54. rounded out by Andy Hebrank "ahebrank" (https://www.drupal.org/u/ahebrank).