Needs work
Project:
Entity API
Version:
7.x-1.x-dev
Component:
Views integration
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Jun 2011 at 07:52 UTC
Updated:
22 Mar 2017 at 15:36 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
drunken monkeyGood idea!
However, I'm sorry but after taking a look at the method (my code, not yours), I just can't stand keeping it that way. Please review the attached patch with this feature, some refactoring and a completely unrelated fix for the entity field handler.
Again, sorry. ;)
Comment #2
drunken monkeyThe Entity API is now responsible for the field handlers – but this is still a good idea (in my opinion). We'd just need to update the patch (if this would be approved by fago).
Comment #3
drunken monkeyJust tried to implement this for the Entity API, but had to realize that list handling for entity-valued fields is broken anyways (at least when using
countorfirst, and the new ones would have had similar problems). Field API fields have their own mechanism and other kinds of fields are a pain to add for testing.So, we should probably first fix the existing method, and then implement this analogously.
Comment #4
nwom commentedSince this issue is a bit older, was wondering if anyone came up with a solution or is this perhaps integrated somehow? Since standard views aggregation does not work, and since the Views Calc module appears to not be compatible with Search API, I'm still on the search for an available option.
Thanks in advance!