Hello,

When creating a new filter for a views page we need to filter by author. We have to choose some authors, about just 10. We use their nickname so it is not so long. But when we try to add the authors in the field "users names" inside the filter "content: written by" we found that there few characters available, only 128 characters, so we cannot add so many writters as we need. Is it possible to enlarge this field so we can increase the number of authors available??

We are using Drupal 8.8.3, testing in Drupal 8.8.5 also and PHP 7.3.6

Thanks a lot,
Regards, Ricardo

Comments

rhsantos created an issue. See original summary.

avpaderno’s picture

Version: 8.8.3 » 8.8.x-dev
Issue tags: -exposed filter
lendude’s picture

Title: Filter Authors is too short » Text field to add Author names filter values on can be too short when needing to filter on multiple users
Category: Bug report » Feature request

Updated the title a bit to make it a bit clearer what the problem is. I'm not sure if I would qualify this as a bug. Even if we up the size it might still not be enough if you have a LOT of user names you want to enter. So this is just about finding a sane default.

So, what should it default to? And if we change it, should we only so so for name fields? of should we update the default value field to be bigger? Other filters could run into this too...and if we change it in the backend, should we also update it for the exposed filters?

rhsantos’s picture

Hi Lendude,

At first I thought it was a bug because when I choose an user, for example, rhsantos, the system adds the id number: rhsantos (89). So I thought this number implies a lot of extra characters per user. As a feature request I also don´t see why it should be a number of characters, because maybe, users can be one character, a,b,c,d, or really long nicknames: jmenende. Why should it be limited by characters? Maybe it should be limited to a number of users, something clear. like, max users: 10. This could be more adequate. In case you need more users there should be a warning to use roles or groups in order to organize the exposed filter. Even more, if there is a exposed filter maybe it should be a list, not a text field?
Another question that I have not tested, whether there is a limit like this in other fields. For example, using workflows states seems to expose all states.

Anyway, thanks again for your attention.
Regards, Ricardo

Version: 8.8.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. 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

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.

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

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.