We finally worked this issue at and it really is more of a documentation issue. If you examine the Index options for each index in the Search API admin screen, there is a "Read Only" option for each index which works as advertised. The issue is that the field is hidden under a closed section and nothing in our experience pointed out this very critical setting.
I realized after the fact that Symphony 7 isn't supported yet, my bad.
butterfi → created an issue.
butterfi → created an issue.
As I've been digging into this issue, I have found several sources that have led me to the belief that Meilisearch really only wants one date. Its my understanding that Meili flattens arrays, which for indexes with Taxonomy fields is fine - the term id gets translated to the label and Meili just parses the whole thing as a string.Thats great for taxonomy terms, but doesn't help populating repeat events. I'll keep poking, but I think for now, I'm going to keep using Views for the Events date
When I index the smart date field ("event date") which typically has repeating events (i.e. held every Wednesday), I get a single event entry with an array of dates, which is I believe is the expected behavior. What I think Meilisearch wants is a separate index line for each event as it doesn't know what to do with an array of timestamps. When creating the Search Index, I can add fields to the 'Content' section, but there are two other sections offered: "Smart Date Overide" and "Smart Date recurring rule" and this is where I'm puzzled. How are these areas meant to be configured? I can add fields to them, but I don't see any impact. I'm not even confident the fields being added have values. (See attached)
Thanks for your time!
butterfi → created an issue.