Follow up for #1801304-313: Add Entity reference field Task C

Problem/Motivation

Have to create an entity reference display in a view. dont enter that until a few screens after started to do it.

Click "Create a view" here. But before doing that, I recommend writing down "Entity Reference display" on a napkin, or else having a really good memory, because the next screen doesn't say anything about it:

Proposed resolution

pass along to the views wizard that we want an entity reference display. Then dont have to "+ Add" it. It's already one.

Remaining tasks

Discuss who to implement this. Is it possible?

User interface changes

No UI changes.

API changes

Maybe API change?

Original report by @webchick

Follow up for #1801304-199: Add Entity reference field 3.

FEEDBACK:
One really positive thing I will say is that throughout, already knowing Views, I was actually to complete this task thanks to the very precise wording in these and other various field descriptions. So bravo for attention to detail and clear use of language here.

Unfortunately, the vast majority of people wanting to build a website out there have not used Views, and if they have used Views they most certainly probably have not messed a lot with Displays, since the wizard takes care of that. :( My first question would be, "Can we just expose the most common things people are likely going to want to filter by (e.g. Users by role, Nodes by type, etc.) on this form right here, without requiring people to jump all the way to Views to do them? I can totally see going to Views for "I want my author credit field to reference users with a certain number of user points and who have created between 1 and 5 articles with the word 'Snoopy' in them" but not for something so basic.

Comments

effulgentsia’s picture

Component:field system» entity_reference.module
Category:feature» task
Priority:Critical» Major

This seems more like UI cleanup than a feature, so recategorizing as a task. Also, it doesn't seem like the kind of thing we would hold up a Drupal release for, so downgrading from critical. It is an important usability cleanup to a pretty foundational site building tool, so I think major is more accurate than normal.

YesCT’s picture

Thanks. I think I made a mistake when I created the follow-up with just copying the priority from the source issue. :)

yoroy’s picture

Complex issue title! :) Seems to be about a disconnect between two screens in views. Any change we could get screenshots of those?