-
Notifications
You must be signed in to change notification settings - Fork 2.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When Creating a new content item in BagPart, content item Index don't update #15226
Comments
That is by design. BagPart items are stored in the same content item not as a related items. In other words, the content items in the bag are not stored in separate document which mean they will not be indexed separately. |
@effapp in the past I faced the same problem, and ended up with some custom index provider, but please remember you can fill up your index very quickly, this solution is also able to index nested BagParts, inside TextFieldIndex in ContentField column you will get something similar to path "Field.NestedName1.NestedName2.NestedName3". In my case I wanted to have all index values in same table (TextFieldIndex) and avoid creating dedicated one.
some extensions:
here it would be good to get rid of those tuples, but it was just a proof of concept:
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the bug
When Creating a new content item in BagPart, content item Index don't update
To Reproduce
Steps to reproduce the behavior:
(Taking OrchardCore.Commerce solution as example)
1.Create a new ContentType and name "BagTestPage", add BagPart in it
2.Set "Contained Content Types" of Bag in BagTestPage to "Product"
3.Create a new Content Item of BagTestPage and name "ProductBags"
4.Create a couple of Product content items in ProductBags, these Product content items was not updated to ProductPartIndex.
The text was updated successfully, but these errors were encountered: