Dealing with Layout Builder + Views + no Search API driven Views (SQL) mixed with Search API views

[DiegoPino]

What?

For many reasons a lot of our code assumes our standard deployment. Search API driven views, no layout builders. But bug reports have come from attempts (on mixed scenarios and using extensions/modules) of Search API results with embedded SQL ones.

There will be other issues, but this one handles on specific, an alter here

https://github.com/esmero/strawberryfield/blob/6d54fd90a94d8a977e3437850a16be9aa218a20c/strawberryfield.module#L342-L344

I am assuming blindly that the node, when the view property and lazy loading is enabled has

• a view property with a views executable object (this is a dynamic property added by a search api result
• The view has a query (I hope so? should be right)
• The query has is from the same index the alter is coming from (the results)... and that is where things get bad

Solution. Check on every accessor. Pull coming

[DiegoPino]

Fixed via https://github.com/esmero/strawberryfield/commit/0d0635c5973f6364935ca8d6904c087b0d31329c