Nested Looper to pull Toolset repeating group 2022

[wowflak]

I am having an issue with a nested looper seeing the Toolset repeating group. I saw someone else bring this up in the forum but with no solution. I cannot use ACF on this site as it is heavily integrated with Toolset fields.

In the looper provider I am calling the repeatable group like this:
{{dc:toolset:field field=“slides”}}

However it does not seem to work. Any ideas on how to get this to work?

Thanks

[marc_a]

Hi @wowflak,

Thanks for reaching out!

Would you mind sharing your admin credentials so that we can on your setup properly? To do that, please give us the following information in a Secure Note.

• WordPress Login URL
• Admin level username and password
• Page URL or Layout Builder name

You can find the Secure Note button at the bottom of your posts.

Thank you.

[wowflak]

Great, creds in secure note.

[ruenel]

Hello @wowflak,

In which page you have added the Nested Looper? By the way, the {{dc:toolset:field field=“slides”}} will not work because toolset is not supported with the dynamic contents. You may need to use the Post Meta instead. Maybe like this: {{dc:post:meta key="slides"}}.

Kindly let us know how it goes.

[wowflak]

I have listed the page in secure note.

[tristup]

Hi @wowflak,

I have checked your website and the settings and found that you are using the Toolset plugin for creating the Custom Fields, you need to exact custom field name to the data into the Dynamic Content. I have checked but didn’t get the exact field name from it, I would suggest you contact the plugin author on this.

Thanks

[wowflak]

I believe that the exact name for the fields is like this wpcf-slides for example. So I added wpcf- to the meta and still no luck.

[alexander]

Hi @wowflak,

I’m sorry, we don’t have support for Toolset fields, so they don’t work out of the box. It might be possible with some custom code to connect the dots there, but would be getting into customizations.

You may have already gathered some of this from your experience with Loopers so far, but let me explain a bit about how Dynamic Content and loopers work together in case it helps in an way.

• When Dynamic Content sees any statement like {{dc:***}}, it runs a registered function and tries to return some data.
• If that statement is in the input for the Looper Provider “Dynamic Content”, it will try to coerce the result into an array. If it’s not already an array, it wraps the item in one.
• If that statement is anywhere else (usually text somewhere) the result is coerced into a string.
• You need to make sure however the field is resolved, it ends up as an array. The post meta example above might not work if Toolset doesn’t store their repeater items as an array.
• You can troubleshoot loopers by adding a Raw Content element somewhere inside the provider and using these statements: {{dc:looper:debug_provider}}, {{dc:looper:debug_consumer}}.
• The key attribute of {{dc:looper:field}} supports dot path notation like {{dc:looper:field key="path.to.thing"}} where each dot reaches into the property of nested object.

So in theory if your top level data is an object, you could consume it and use a {{dc:looper:field}} to reach down to find the actual array, then point that into another Dynamic Content provider. Unfortunately you may end up with a convoluted tree of elements in that process. We have some improvements planned for Dynamic Content that will let you nest statements which should simplify things a bit more.

I’m sorry I don’t have a more concrete answer. Our current Toolset integration is a very raw way to access fields and wasn’t really meant for anything past getting strings.

[wowflak]

Thanks for the explanation. I will see what I can figure out

[ruenel]

You are most welcome, @wowflak.