I'm trying to have my styling and templating be more consistent across my site by using WordPress FSE features, like Patterns, etc, but they really don't like using Toolset Views, or perhaps it's the other way around. However, when I try to use Query Loops instead, the Toolset Dynamic Content doesn't recognize the query loop's direction of which page to look at, at all.
Is there a way to force Dynamic Content, either through a code snippet or otherwise, to look for direction from Query Loops, in addition to whatever trigger there is for Views? I'd also like to use the Advanced Query Loop plugin, which I assume works the same way as the vanilla WordPress version.
However - the good news is that our Devs will work on this very soon and try to make it working as soon as possible, maybe we can make it possible with the next release. However, I do not have any exact timeframe when it will be possible but you can expect it in three-four months from now on.
That errata doesn't speak to interoperability with WordPress Query Loops. Is that on the roadmap, as well? Is there some hack I can use in the meantime to have Toolset blocks look for information from the Query Loop?
For now, Toolset Blocks will not work inside WordPress "Query loop" block but our Devs may look at it in order to find if any possible solution available but there is no ETA on it.
In addition to that - I do not have any workaround to share.
