Add support for a wildcard parameter and a case sensitive option

Created on 18 July 2018, almost 6 years ago
Updated 27 March 2024, 3 months ago

There should be a possibility to provide a wildcard as a parameter value, so any value for certain parameter gets matched.

Also, lowercasing provided parameters and their value by default is an inflexible option, as certain parameter values can be case sensitive (e.g. All (- Any -) value in views exposed filters etc.)

✨ Feature request
Status

Needs work

Version

1.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium n3uronick

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • πŸ‡¦πŸ‡ΊAustralia Feng-Shui

    This is a re-roll against the issue branch for 3286634 which provides D10 support.

  • πŸ‡¦πŸ‡ΊAustralia Feng-Shui
  • πŸ‡¨πŸ‡¦Canada plousia

    Thanks for this patch, this gets me sort of partway to what I need. Two things would be really useful:

    1. The ability to combine positive and negative conditions. E.g. for my use case I want to show the block on the first page of a paginated view only, but not any following pages. This sort of works by setting the block visibility to the root url in the normal page visibility setting, and exclude others using Condition Query and this patch with page=* and checking "negate the condition". But this doesn't work if someone follows the pagination link to the first page, as it uses the query string page=0. It would be nice to be able to specify visibility only on the query string page=0, but exclude all others.

    2. This leads me to the second useful feature, which would be ranges. If I could do the above plus specify exclusion of a range, e.g. pages 1 to end, that would be perfect. I get the idea you can exclude pages for example with page=*\1,2,3 etc., but it's not possible to keep up with entering exact page numbers on a site with a large amount of content which is being constantly added.

  • πŸ‡§πŸ‡ͺBelgium Fernly

    This patch introduces a new bug with D10. See this facets issue fixing the same bug: Drupal 10: InputBag::get() may no longer return an array in Symfony 6

    Rerolling the patch against 1.x-dev.

  • what is the current state of this patch? would be nice, to have this future in the stable version of the module.

  • Open in Jenkins β†’ Open on Drupal.org β†’
    Core: 10.2.1 + Environment: PHP 8.1 & MariaDB 10.3.22
    last update 3 months ago
    12 pass
Production build 0.69.0 2024