Closed (fixed)
Project:
Search Overrides
Version:
8.x-1.3
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Aug 2019 at 13:21 UTC
Updated:
4 Jul 2020 at 13:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mandclu commentedSounds like a great suggestion. If we could get this and #3059864: Allow selecting other entities besides nodes done, I think that would justify an 8.x-2.x release.
Comment #3
mandclu commentedThinking about this some more, the override should currently apply globally anyway. The path in the global configuration is just for use in the "Test Override" button. Theoretically you could update that to accept multiple values (with labels at that point) and then offer multiple links to test, but it's really just there as a convenience, since all it really does is run a search for the term.
As such, if anything we might consider the opposite: the possible for any override to make it ONLY apply to a subset of the defined indexes. Would that be of value?
Comment #4
barrett commentedMandclu, to confirm, you're saying the path and URL paramer values in the form at `/admin/config/search/search_override/settings`are only used to provide test and preview results for the overrides and do not restrict overrides from being applied at other paths. Correct?
It might be worth adding some text to the form to clarify that, if it is indeed the case. Just looking at the form, I had drawn the same conclusion as @mpp; that the overrides would only take effect at that url.
Comment #5
mandclu commentedPerfectly reasonable request. I should be able to get that change made shortly.
Comment #6
barrett commentedHere's a first pass at wording
Comment #7
mandclu commentedTweaked your wording, and also tried to make this more explicit on the settings fields themselves. Skipped the interdiff since it was almost identical to the patch.
Comment #8
barrett commentedPedantic of me but, since you changed the title of the path field to include 'for Preview', should the title of the parameter field also change? Either way, this looks good to me.
Comment #9
mandclu commentedI will confess, I debated about that myself. The other thing I considered was creating a fieldset called "Result Previews" or similar, and putting the fields in there.
Comment #10
mandclu commentedI decided to explore that approach, and like the way it turned out, though the description text ends up being a little less field-specific.
Comment #11
mandclu commentedComment #13
mandclu commentedSince we're still at alpha for the new release, decided to go ahead and get this merged in. Feel free to reopen if you think additional tweaks are needed.