One possible solution could be to remove html when indexing. This can be done by adding the [RemoveHtmlTagsWhenIndexing] attribute to the relevant property.
Well the strange part is that this is a vidoeId part of a videofile and we have an indexing convention excluding videos (by interface on MediaData)
ContentIndexer.Instance.Conventions.ForInstancesOf<MediaData>().ShouldIndex(x => false);
So should I need to state Exclude vidoes and ignore html?
This kind of information should not have been indexed in the first place.
Its two "bugs" in one
So whats basically is going on here is that we successfully have excluded the video to be indexed, checked and its not in the index.
A page that have the video in it gets indexed and all the properties from the video as well..
So in my case [JsonIgnore] should do the trick?
I can live with that
I cant accept the fact that the search highlighting takes parts from html tags attributes etc and index them as part of content on a page.
The information 1234 is getting indexed and displayed as a highlighted text
Is this a bug or a feature? How can we disable indexing of attributes inside elements.
I consider this not to be content and shouldnt be indexed at all.
Live example can be provided by PM