Allow all valid URL characters for custom search path

Created on 9 November 2022, over 2 years ago
Updated 21 February 2024, about 1 year ago

Problem/Motivation

I have successfully got Search 404 working nicely now thanks to @emilymathew but is doing so, I uncovered what I think is an important glitch that needs sorting.

I actually have several different Search API views in my site which sit off of different paths but all of which are 'flavours' of a search

Thus, they are...

  • search-staff
  • search-student
  • etc.

Given this requirement, it' clear that I needed Search 404 to allowing em configure a Custom search that fell back to one of these and for me that would be the more restricted search-student one.

HOWEVER, entering ...

search-student?search_api_fulltext=@keys

...as the path lead to the dreaded...

Custom search path should not contain special characters other than "/?=_".

I can't see any obvious problems with allowing (frankly) any number of dashes in the actual path so maybe we should roll that out in the current dev and next release?

After all, we can't always assume that the Search API path with be just a single word.

Thanks to everyone for ongoing attention to this superbly useful module.

🐛 Bug report
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

🇬🇧United Kingdom SirClickALot Somerset

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

Production build 0.71.5 2024