Pro 6.1.2 - Loopers on archive page issue

Beta
#1

@charlie sorry for tagging you. Added this to the beta by mistake. Not sure if it can be moved.

I have a page archive which displays all the shop products. The products loop is set up with a consumer.

In the consumer I want to display all the shop categories the product belongs too.

This is where things go weird.

Before I add the looper provider for the shop categories I can get all ACF fields from the product, I am also able to access things like the Product title either via {{dc:post:title}} or {{dc:woocommerce:product_title}}.

If I add a looper provider above all the product info then after the looper provider I can no longer access the products ACF fields and I can only access things like the product title with {{dc:woocommerce:product_title}}. I can no longer access the info via {{dc:post:title}}.

The structure below does not work. I need this to work

Looper Consumer for the archive
  
   Looper Provider for the product categories
    Looper consumer for the product categories

{{dc:post:title}}
{{dc:post:permalink}}
{{dc:post:permalink}}
{{dc:acf:post_field field="acffield"}}

If I remove the Looper Provider / Consumer for the product categories or move the dc:post or dc:acf field above the looper provider / consumer then the above works.

This example works.

Looper Consumer for the archive
{{dc:post:title}}
{{dc:post:permalink}}
{{dc:post:permalink}}
{{dc:acf:post_field field="acffield"}}

And this example works.

Looper Consumer for the archive

{{dc:post:title}}
{{dc:post:permalink}}
{{dc:post:permalink}}
{{dc:acf:post_field field="acffield"}}
  
Looper Provider for the product categories
    Looper consumer for the product categories

Is there a way to sort of reset the consumer or to get the structure I want working?

#2

This might be easier if I see it live. I think I get the point though that stuff gets funky when using Default provider and having a looper inside that. I’ll have to try it out next week. I’m not sure if we can move topics, but you are free to create a new one if you need an answer this weekend.

#3

I’ve added a secure note.

#4

I think my post is the same thing that is going on here.

#5

We’ll have a fix or workaround for this in the next release. It’s related to the issue, that example you posted just retriggers the issue from happening again. Thanks, I’ll keep you updated if you need to do anything.