Vulnerability in EPiServer.Forms
We are indexing the POCO object on our site. We need a language-based find the index.so we inherited the EPiServer.Core.ILocalizable class in our index class.
public partial class SearchResultItem : EPiServer.Core.ILocalizable
After indexing, we didn't see any language-based index in find backend UI. Refer image in below link
Have you enabled/selected language while creating service in https://find.episerver.com/ ?
I am using epi find demo index only and enabled English and Spanish languages.
It may be relative, like you need to listen for events on changing any data and trigger reindex your POCO object. Please see below link if you get any direction (I know it is related to catalog but might be helpful)
Refering to your image, «CMS Content» is a h1-heading and «Language branches» is a h2-heading. I think only CMS-content is divided into language branches. You have no CMS content indexed, so you have no language branches indexed. Makes sense?Also, I think the languages you specify in the image in Praful's image only affect stemming etc in language-specific queries:https://world.episerver.com/documentation/developer-guides/find/NET-Client-API/searching/language-specific-queries/You may index content created in other languages.When implementing ILocalizable, you have added implementations for Language, MasterLanguage and ExistingLanguages?
Thanks Tomas,Yes, it makes sense. Just checked with CMS content now I can able to see language branches.I am just doing POC with language-based indexing for POCO objects.ILocalizable - Yes I implemented that 3 properties.So When we index POCO objects with different language then the language branch will not be shown. Is this right?