OrchardCMS
Populate IndexingTask table after creation (#5466)
Proposed solution to fix #5466. When OrchardCore.Indexing module enabled, IndexingTask table should contain record for each ContentItem. But if I enable OrchardCore.Indexing module when system already has content items, i need to republish them to make them available for indexing. That is not so simple if you have hundreds of items. This change will populate table with required data during creation. Or in case if system already has gaps in IndexingTask table it will be fixed during migration from version 1 .
I would rather have a button in the admin UI to execute that same SQL Query. Else, we never know when someone will disable the OrchardCore.Indexing feature and enable it back a couple days later. Then you will miss all the documents published in these days and will have no way to execute this Query again. Also, it should insert only records that are not already there to not create duplicates.
@Skrypt It is a good point to have ability to run it in any time. Do you have any suggestion where this button should be placed?
As for "Also, it should insert only records that are not already there to not create duplicates." - it is already covered in this PR.
I think you will need to create a new configuration page in the admin UI.
(admin menu) Configurations --> Indexing
New drivers and views in the OrchardCore.Indexing module.
We need to keep the migration code but we should extract the scoped db request code into something like a Mediator command.
@sebastienros Are we using anything like https://github.com/jbogard/MediatR in OC yet. Do you have a preference over a specific library? I know .NET 9 should have it's own thing too. Is it usable in OC right now?
This pull request has merge conflicts. Please resolve those before requesting a review.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Do you have any suggestion where this button should be placed?
This can be kept automatic if you implement a different event than migrations. There is an event to detect a feature is enabled (this is what migrations use).
This pull request has merge conflicts. Please resolve those before requesting a review.
It seems that this pull request didn't really move for quite a while. Is this something you'd like to revisit any time soon or should we close? Please comment if you'd like to pick it up.
Closing this pull request because it has been stale for very long. If you think this is still relevant, feel free to reopen it.