Jasmin Savard
Jasmin Savard
Some of these IndexingConstants are based on what ElasticSearch does by default. Changing this means changing the default naming convention of ElasticSearch. As for the ContentItem it is a question...
It is probably missing a new UpdateTo for each modules Migration to alter their database. Though, it may not work if ContentItemVersionId's are null in that database. I would rather...
Yes, the breaking change is that you can't set a db column to non-null if there are null values in it. Basically, we would need to repopulate all the non-null...
@piedone This PR is one of those breaking changes that may be necessary for QOL in OC at some point. I can't push more time on it right now but...
@hishamco Update your node.js and/or npm to latest LTS version.
Once you installed the new node.js and npm try and do a cleanup of the node_modules folder. Then redo npm install.
Sometimes I do a `git clean -xdf` to clean also the package-lock.json files and retrieve those from the repository. It can be a node_modules cache on your computer too. There...
This should work after merging https://github.com/OrchardCMS/OrchardCore/pull/13721 as it will no longer do a SQL query in the LuceneIndexingContentHandler. Though same logic needs to be replied in ElasticIndexingContentHandler and AzureAISearch one...
Here is the example that we have in Orchard 1 where we use an AJAX call to the controller action so that we don't hit a "request timeout" issue as...
You can create a different CSS style that will be applied on print. ``