Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I know I had this before but we usually use Chosen to fix such issues for customers:
Reproduce
Go to your user profile, section "Drupal" and try to add user rokr as your mentor. (Yes, that's the complete user name.)
Autocomplete only lists up to 10 results containing "rokr" - and these are obviously quite a lot.
Workaround
Grab the user ID and type [username] ([uid]) to add your mentor in similar cases.
Solution
Either we fix this on a core level (no idea about the implications) or we use a contrib module for this field's configuration (no idea about the update strategy and possibly resulting decisions against more modules). Chosen has a config option for the amount of results.
Comments
Comment #2
dddave CreditAttribution: dddave commentedComment #3
drumm#2613430: Mentor autocomplete: 10 results is not enough looks like what we would want. This field is managed by the Entity reference module.
Comment #4
drummI mean #1700112: Entity reference list View Pager: Items to display is broken.
Comment #5
YesCT CreditAttribution: YesCT commentedComment #6
apaderno10 is probably a too low limit, but there is a bigger issue: The autocomplete uses what entered to find usernames ending with that string. So, if I enter kiam, I don't even get a name starting with k. With a complete username like dalin, it returns all the usernames ending with dalin, instead of returning the only username that exactly matches dalin.
Entering a username starting from the beginning is probably more common. Assuming that what entered is at the end of the username is causing problems, and I cannot imagine doing the same when looking for a node title.
Comment #8
drumm#1700112: Entity reference list View Pager: Items to display is broken is now RTBC, that’s good enough to deploy to Drupal.org. It leans on Views to configure the number of items to display, so drupalorg needs that View created.
In the meantime, matching on starts with instead of contains is an excellent idea.
Comment #13
drummThis has been merged & deployed.