Right now it looks like an entity module such as Profile2 has this choice:

- go with the views support EntityAPI provides, which may not do all it needs
- do everything itself

It would be better if Profile2 and other modules could build on EntityAPI's base rather than have to repeat it.

Comments

bojanz’s picture

bojanz commented

My patch at #1077148: add an entity-view row plugin allows you to override handlers (or disable them completely) from the property info of each column.
For everything else, there's hook_views_data_alter().

daften’s picture

daften commented

subscribe

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

>It would be better if Profile2 and other modules could build on EntityAPI's base rather than have to repeat it.

They can, just extend the provided controller class + specify that controller in hook entity info. That's the way it works for all the entity api controllers.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.