Don't have full reproduction steps yet - I haven't been able to identify the trigger for this broken state, but have worked out part of the underlying issue.
When a user adds a custom content rule, it should update or create the file ContentRuleList-userFilters. There appears to be a state that Orion can enter into (likely from adding other custom rule lists, or perhaps adding custom rules), whereby even with the custom rule list enabled, the entered rules are not transposed into a ContentRuleList.
When this happens, you can see that even with a custom rule entered, and custom rules enabled, it's not applied (and the userFilters file isn't created).
I tested by removing the userFilters file (which was not being updated) and replacing it with a "working" one, and the filters behave as expected - the issue therefore appears to be the logic through which Orion decides whether to update the userFilters, based on the UI state.>!!<
When the checkbox for "Custom Filters" is ticked, Orion RC should always be updating the underlying ContentRuleList.
There is some state that the app can enter where this doesn't happen. I've not worked out exactly what causes it, but when this state is entered, you can see and verify that the userFilters ContentRuleList is not being written as expected.
In a working setup, the file is written as you would expect.
0.99.126.2-rc
Sonoma (14)
