I believe that once you turn on multi-language features the indexes change and append the culture code to the end of their field name (only on the multi-lingual fields) ... so if your bodyText is now multi lingual and is available for both English(UK) and Welsh(UK), I believe 2 fields now exists in the index:
bodyText_enGB and bodyText_cyGB
If you update your search query to take this into account it should start working I think.
I was going through this approach, for creating an custom index for multi language, but in my case the index creates only for one default language not for any other variant enabled language.
the index are not created by appending the lang code, as illustrated above. but i can see that its created for multiple lang for other type of indexs.
Below is my code snippet:
public void Initialize()
{
if (_examineManager.TryGetIndex("ExternalIndex", out IIndex externalIndex))
{
//initalizing the custom index for Article document type. Fileds Category, Tags and Author
externalIndex.FieldDefinitionCollection.AddOrUpdate(
new FieldDefinition("searchableCategoryTagAuthor", FieldDefinitionTypes.FullText));
((BaseIndexProvider)externalIndex).TransformingIndexValues +=
IndexerComponent_TransformingIndexValues;
}
}
Did you ever figure this issue out? Currently trying to get past this myself with custom index fields and can't seem to reliably access the current culture of the node being indexed.
Site search in site with language variations
Hi all,
So, I successfully migrated my site from Umbraco 7 to 8. Initially I also managed to make my search feature work again.
Then I implemented using language variations. Now the search does not work.
My goal is to search the site (ideally in just the "support" section) and show the results. But only per language.
The current code follows:
The above code consistenly returns zero results.
I hope someone can help my in the right direction. Thank you!
Hi Kasper,
I believe that once you turn on multi-language features the indexes change and append the culture code to the end of their field name (only on the multi-lingual fields) ... so if your
bodyText
is now multi lingual and is available for both English(UK) and Welsh(UK), I believe 2 fields now exists in the index:bodyText_enGB
andbodyText_cyGB
If you update your search query to take this into account it should start working I think.
Thanks,
Nik
Hi Nik,
Thank you very much for directing me here.
I checked the index via backoffice and indeed the results are sorted in languages per fields. bodyText is now bodyText_da-dk for Danish edition.
I'll continue work on this to accomodate the different languages.
Hi Nik,
I was going through this approach, for creating an custom index for multi language, but in my case the index creates only for one default language not for any other variant enabled language.
the index are not created by appending the lang code, as illustrated above. but i can see that its created for multiple lang for other type of indexs.
Below is my code snippet:
setting values for custom index:
searchableCategoryTagAuthor my custom index name:
Any help would be greatly appreciated !
Thanks, Gurumurthy J V
Hi,
Did you ever figure this issue out? Currently trying to get past this myself with custom index fields and can't seem to reliably access the current culture of the node being indexed.
Thanks Andrew
is working on a reply...