Usability bug,

The text "search fields" in the settings for an entity reference view is not clear and needs to be disambiguated from "search" .

As I understand it what the user is doing here is selecting which fields will be added to autocomplete in the form, therefore the text the user should see would be something like "Show these fields in autocomplete".

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tkoleary created an issue. See original summary.

jhodgdon’s picture

Title: Entity reference view "search fields" is not clear » Entity reference views setup -- "search fields" is not clear
Version: 8.0.0-beta15 » 8.1.x-dev
Component: views.module » entity_reference.module
Status: Needs work » Active
Issue tags: +Usability

Fixing tags, status, component, version.

amateescu’s picture

Version: 8.1.x-dev » 8.2.x-dev
Status: Active » Needs review
FileSize
759 bytes
22.76 KB
23.48 KB

Seems like a small improvement to me :) Moving to 8.2.x because of the string change and also adding some some before/after screenshots.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jonathanshaw’s picture

Status: Needs review » Needs work

I'm afraid you're misunderstanding what those settings do.

They control what fields on the entity are queried to match the entered text. See drupal/core/modules/views/src/Plugin/views/display/EntityReference.php ->query() for how they are used.

Currently no settings on the view affect what is displayed in the autocomplete (it's hardcoded to show only label), but this is fixed by #2174633: View output is not used for entityreference options.

I agree the current wording is less than wonderful.

jibran’s picture

Component: entity_reference.module » entity system
tkoleary’s picture

Status: Needs work » Closed (duplicate)

@jibran

You're right, this is a duplicate.

@jonathanshaw

Moving your comment to the other issue