Closed (fixed)
Project:
Entity API
Version:
7.x-1.x-dev
Component:
Entity CRUD controller
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
1 Jun 2011 at 17:10 UTC
Updated:
8 Aug 2011 at 08:23 UTC
The auto-provided entity-relationships to
* add an options-list to the filter of machine-names of exportables (offer select drop-down of all entities)
* provide an additional filter that works without a join for bundle-relations and exportables (again with select)
* for bundle relations, maybe add an option to restrict the relationship to a certain bundle directly to the relationship
Comments
Comment #1
joachim commentedI've not been following developments that closely... does/can this handle the sort of thing done at #1114454: Views integration: create an entity-entity relationship that limits by entity type if applicable?
That is, a relationship from foreignEntity to OurEntity produces duplicate rows due to there being a one to many relationship, and so the relationship handler to go from foreignEntity to OurEntity needs to present UI options to limit the relationship by one or more types.
Comment #2
fagook, I took a stab on that and commit some improvements.
I've add fields/filters/arguments/sorts for fields that represent relationships + improved filters to make use of any options lists specified in the entity property info. Thus, that fixes points 1) and 2) from the issue and in my tests works fine for the profile-profile type and profile-user relationships.
#1
As I described in http://drupal.org/node/1114454#comment-4508784 you can use a relationship + a filter on that relationship e.g. to filter for a certain bundle.
But as written in point 3), it would be nice to have an option to directly filter for a certain bundle when you add a relationship. I guess we would have to provide another relationship handler for that, so I leave this open for a possible follow-up issue for now.
Comment #4
bochen87 commentedsubscribe
Comment #5
fago