Currently using v4, beta 1 as we require facets for our Umbraco 12 project, and I've come across an interesting issue.
We have content items based off a document type for news posts, and our site has three languages. English is the default, non-mandatory language. German and Italian are the other languages content can be created in, with English set as the fallback.
The behaviour we've observed is that if you were to do an full external index rebuild, via the umbraco backoffice > settings, content items that only have versions in German and/or Italian (but not in English) will not be indexed. However, if I was to publish these content items individually, they get indexed.
Articles that have an English version get indexed irrespective of whether they are published individually, or an entire index rebuild takes place.
I have debugged the PublishedContentIndexPopulator and can see that the content is being passed to index.IndexItems to be indexed. Furthermore I have also debugged the ContentValueSetValidator and can see that the value set is valid, and identical to the value set that is generated when the content is published directly. So thinking the issue lies somewhere in examine after the call to IndexItems?
Hi,
Currently using v4, beta 1 as we require facets for our Umbraco 12 project, and I've come across an interesting issue.
We have content items based off a document type for news posts, and our site has three languages. English is the default, non-mandatory language. German and Italian are the other languages content can be created in, with English set as the fallback.
The behaviour we've observed is that if you were to do an full external index rebuild, via the umbraco backoffice > settings, content items that only have versions in German and/or Italian (but not in English) will not be indexed. However, if I was to publish these content items individually, they get indexed.
Articles that have an English version get indexed irrespective of whether they are published individually, or an entire index rebuild takes place.
I have debugged the PublishedContentIndexPopulator and can see that the content is being passed to index.IndexItems to be indexed. Furthermore I have also debugged the ContentValueSetValidator and can see that the value set is valid, and identical to the value set that is generated when the content is published directly. So thinking the issue lies somewhere in examine after the call to IndexItems?