Different syntax for an ACF looper field returns a different value

[pvallaeys]

I am used to the syntax {{dc:looper:field key=“row_options”}} to retrieve ACF fields in a looper. However, when using the drive icon to retrieve the field, it generates the syntax {{ looper.field({“key”:“row_options”}) }}.

Interestingly the result is different when the ACF field is a Checkbox set to return the value.

In the first case it returns a comma delimited field with the checked boxes. In the second syntax it returns an Array instead as shown in this screenshot. In the screenshot I omitted the first “{” in the syntax to display the syntax used without calling the ACF field.

It took me quite some time to figure out what was happening. Is this a bug or did I do something wrong?
Thanks for looking into this,
Patrick

PS: If you can’t reproduce the problem and need access to the site, let me know.

[ruenel]

Hey Patrick,

Thanks for writing in! The {{dc:looper:field key=“row_options”}} format is the default of the dynamic content. When you enable the TWIG feature in the Theme Options > Globals > Options > Twig, the syntax of the dynamic content will then become {{ looper.field({“key”:“row_options”}) }}.

The return value may differ because of how Twig handles the custom field. You can make use of the {{dc:looper:debug_consumer}} to check on the returned data and use that to get the exact looper field to display on the page.

Best Regards.