I have a pretty complex structure of bloqs fields.  And on some templates, I’m using the bloqs tag pair multiple times on the same template (some small parts of bloqs content is being displayed as title/header content on other areas of the template outside of the main bloqs content).

When bloqs caching is enabled, the templates with multiple tag pairs of the same bloqs field do not render correctly.  The first instance of the bloqs field tag pair is cached, then that content is reused further down the template, even though the content being displayed is different.

Would love to either have bloqs naturally support this, or to add a tag pair parameter (key, or tag like speedy, or bloq id, or other identifier) for the caching to be able to distinguish between the different uses on the same template.

Example use.  You’ll see three different positions for the {vendor_team}{/vendor_team} component bloqs field.  The first two, I’m just displaying info about the venue.  The third instance, I’m showing the complete vendor team.

Because the first instance of the bloq field is cached, position #1 displays correctly when cached. But, positions #2 and #3 are not displaying because their fields and structure are not used in the position #1 tag pair.

Position #1:
Using this in a breadcrumb at the top of the page to show just the venue
{vendor_team}{block_venue}{vendor}

Weddings / {wedding_location:city}, {wedding_location:state} / {vendor_name} / {title}

{/vendor}{/block_venue}{/vendor_team}

Position #2:
Using this as a subhead for the page under the Wedding name, showing just the venue

{title}

{vendor_team}{block_venue}{vendor}

{vendor:title}

{/vendor}{/block_venue}{/vendor_team}

Position #3:
Using this to show the full set of the bloqs fields for the vendor_team component.

Wedding Vendor Team