Mário Nunes

I also have the same issue, happened when trying to update from 4.3.0 to 4.3.4

> If you are using the ContentManager to update your content item it should re-index properly. Are you updating the content item with the OrchardCore.Content API or is it done...

Angular 13 is out now :) Also #449 would be great

Thanks for raising this! Currently the code for How-tos and Research is tied up with FilterSorterDecorator. But each module has specific needs which leads to some hardcoded conditions. hardcoded properties:...

As of now, I haven't found a blocker for using the firestore api for our search. It's not ideal, but I haven't found a better solution that wouldn't either cost...

> could be done in a smaller prep PR separate to the search work here. But doing it on a separate PR would mean to modify the code of all...

> Thanks for sharing @mariojsnunes, would you be able to define what you mean by `service` here? Just a collection of methods for doing API requests (firestore in this case)....

this is a major breaking change! how is it still not fixed after 2 months?

Okay, glad to hear, in our case it's triggered by UI only, so should be good. We are stuck because cannot downgrade due to another issue.

Hi, I've been looking into this. Sorting needs a firestore index. Is that possible? Which fields should allow sorting? I have already done some draft code: https://github.com/ONEARMY/community-platform/commit/526a2dfa33cf12bf79f5b072bb9edcfcb0344034 Or is it...