On multilanguage sites we are using views as a source for entity reference field widget to be able to restrict possible tags due to sites language. We have configured views to display 25 items. In node creation backend there will be only 10 items displayed. This prevents editors to choose certain tags, as they won't be displayed.

I have attached some screenshots to illustrate this.

In views entity reference displays it is possible to configure paging options. I tried to deal with them to solve the problem above, but found out, that they are unsupported in entity reference field widget. It would be nice to have an endless scroll option for editors to handle situations where there are many tags. I wonder if this is an error, that views offers paging in entity reference displays or is the reason only, that equivalent functionality is not supported in entity reference field widget by now?

CommentFileSizeAuthor
#2 2759937-2.patch986 bytesdawehner
SPO-view-ref-entity-widget-field-config.png193.3 KBR.Hendel
SPO-view-ref-entity-widget-backend.png281.42 KBR.Hendel
SPO-view-ref-entity-widget-frontend.png294.02 KBR.Hendel
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

R.Hendel created an issue. See original summary.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner for comm-press commented
FileSize
2759937-2.patch986 bytes

The basic problem here is that the autocompletion code always passes along the amount of items, see \Drupal\Core\Entity\EntityAutocompleteMatcher::getMatches

One thing we could do is to take into account the amount of items, in case we have passed in exactly 10, aka. the default value. On the other hand this is still kinda hacky.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner for comm-press commented

Note: The Entity reference views module now has the same kind of workaround applied.

R.Hendel’s picture

R.Hendel CreditAttribution: R.Hendel at comm-press commented

Thanks, @dawehner.
We've applied the patch and it works like expected.

Version: 8.1.3 » 8.1.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.1.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: -entity reference field, -Views Entity Reference +Bug Smash Initiative

@R.Hendel, Thank you for reporting this problem. We rely on issue reports like this one to resolve bugs and improve Drupal core.

Is this still a problem?

Is anyone having this problem on a supported version of Drupal?

Since we need more information to move forward with this issue, I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Kristen Pol’s picture

Kristen Pol
she/her
Primary language English
Location Santa Cruz, CA, USA
CreditAttribution: Kristen Pol at Itty Bitty Byte for Salsa Digital commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than a year ago.

Since there was no additional information provided since the issue was postponed last year, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

Thanks!