Postponed
Project:
Drupal core
Version:
main
Component:
locale.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 May 2014 at 10:23 UTC
Updated:
22 Jan 2026 at 11:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
geek-merlinPatch flying in. D7 for now.
Comment #2
geek-merlinNow really.
Comment #3
geek-merlinPatch flying in: D8
Comment #4
geek-merlinHups, % is still escaped.
* "Leave blank to show all strings." is a lie now.
* Use % as default search string.
Will work later on this.
Comment #7
geek-merlinAgain first 7.x
Comment #8
geek-merlinSmall improvements and fixed tests.
Comment #9
geek-merlinSame for 8.x
Comment #10
geek-merlinSimplytested both patches. Translating is now fun again!!
I'm not too proud of this help string. Improvement appreciated.
Comment #12
geek-merlinFixed last test. Hopefully.
Comment #13
geek-merlinComment #14
nicrodgersThis seems like a step backwards in UX to me, as you're optimising for a use-case that's not very common. The net result is more complexity for the majority of users and searches.
An alternative would be to leave the existing search as-is, and create an Advanced Search page (maybe as part of a new contrib module?) with additional options for searching in a variety of ways.
Comment #15
geek-merlin#14: Good point.
Of course it would be even better to have advanced search options in core ;-).
Comment #27
smustgrave commentedPostponing for a subsystem maintainer to take a look and give their thought.
Comment #28
geek-merlinLooking at it today, i see a different, backward.compatible way to implement this:
"You can use '^' / '$' to anchor the search at the start / end of the string, respectively."
Comment #31
anybodyStill valid and has no subsystem maintaner review 3y later ... ;)