Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
AI OnAI Off
Replacement for PageLanguage Property in PageData ?
I would setup an extension method or a readonly property that returns something that works well with Find filtering and the input data in question.
Jun 08, 2018 23:52
I agree with Johan, you should/can add an extensions method that converts the list of cultureinfo to a list of strings (I do not think ToString do that) and add that to the indexeing and then filter on that.
Jun 11, 2018 7:08
This has been resolved Using ExistingLanguages() from EPiServer.Find.Cms instead of the ExistingLanguages property from the EPiServer.Core.PageData.
It returns IEnumerable<string> instead of IEnumerable<CultureInfo>.
The final codebase looks like this,
.Filter(x => !((PageData)(object)x).ExistingLanguages().MatchCaseInsensitive(lang))
Jun 12, 2018 8:48
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
PageLanguages property in PageData is deprecated.
It suggests to use ExistingLanguages property instead of the PageLanguages.
However, when comes to the filtering, previously the language filtering has been handled by
But when used the below,
it gives a different result.
How to get the same result as before by using the ExistingLanguages property (or from other property)? Thanks in advance.
Note: I am working on EPiServer.Find.Cms --> 12.7.1.0 , CMS ---> 11.5.1.0