-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search Form does not show up when using Azure Search AI #15033
Comments
Shapes not instanciated or it throws a NRE somewhere. Would need to debug it. |
@Skrypt shapes are instantiated from the Search module not the Search provider modules. Also, there is not error in the logs. The fact that everything works as expected in TheDefault theme tells me that the code is doing what it suppose. I am just puzzled with why the BlogTheme experience this behavior. TheBlogTheme is created using Liquid where as TheDefaultTheme is using Razor. I am not sure if this is an issue. I do not see any special liquid helpers that depends on the search providers either. |
I figure out the issue finally. Each provider was registering this independently
|
Yes these are ShapeViewModels ... strongly typed ones. |
There is a bug in the
TheBlogTheme
theme that I have no explanation for as of now. If you enableAzure Search AI
andSearch
features, the search form does NOT show up.To workaround this issue, you have to enabled either
Lucene
orElasticsearch
features for the search bar to show up.When the request is made to
/search
endpoint, the line is reached https://github.com/OrchardCMS/OrchardCore/blob/main/src/OrchardCore.Modules/OrchardCore.Search/Controllers/SearchController.cs#L91which returns the Search.cshtml view https://github.com/OrchardCMS/OrchardCore/blob/main/src/OrchardCore.Modules/OrchardCore.Search/Views/Search/Search.cshtml
That view would render
Search__List
shape, which then rendersSearch__Form
andSearch__Results
shapes. What could be causing this views not to render?Everything works using other themes like TheDefault theme which tells me that there is something about the blog theme that isn't working as it should.
@Skrypt Do you have any idea why this could be happening?
The text was updated successfully, but these errors were encountered: