Search Form : Allow to override Index used #11165
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Guys who have write access so please merege that work: Pull Request here : #11165 please. |
|
@saleemhaq please don't push the team, all the OC dev have permission, but every PR should be validated from different anglee, some may take hours and some may takes months to get them merge I advice you fork the repo and apply these changes if you are in urgent case, otherwise be patient until the reviewer approve this |
jtkech
reviewed
Feb 12, 2022
src/OrchardCore.Modules/OrchardCore.Lucene/Controllers/SearchController.cs
Outdated
Show resolved
Hide resolved
jtkech
approved these changes
Feb 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #11164
Allows passing a QueryString param in the search form page to override the current default Index used for displaying results. This can also be set as a hidden form input fixed value if used from a different form. These Indices are protected by permissions so it should be fine to allow to do this instead of needing to create a different controller per index required to be searched from.
Usage : /search?Terms=moon&Index=BlogIndex