There’s a repeater functionality on section blocks that is not supported with the new theme blocks. Does anyone know if this is on the roadmap to be supported?
The existing repeater functionality allows an admin to populate a dynamic source at the block level and if that dynamic source is a list of metaobjects it will repeat the block for each metaobject in the list.
Block Dynamic Source Unpopulated
Block Dynamic Source Populated with a List of Metaobjects
hey @Matt_Power
When you say new theme blocks, do you mean blocks that are located in blocks folder and rendered as
{% content_for 'blocks' %}
Is that what mean?
@Eugene_Kasimov that is what I’m referring to as theme blocks. The screen shots are an example of the functionality that exists for section based blocks and what I’d like to use with theme blocks.
Just bumping this, as I have the same issue. Might be me misunderstanding some data points though.
“FAQ: Collapsible tabs” uses theme blocks.
“Collapsible tabs” is a normal “old-school” section.
“FAQ: Collapsible tabs” and “Collapsible tabs” has the same settings, so do “FAQ Set” and “Question”.
“Question”-block can be repeated by metaobject entries (or whatever) but “FAQ Set” can’t.
Am I missing something, is this a bug or is it intentional? 
Seems like it’s intentional, as it’s also not available in the reference theme.
@Eugene_Kasimov would be great if it was possible to repeat these blocks based off list data, like metaobject entries.
bumping this up. Is this something planned down the road?
@Arthur_Demurger @mxstbr we’ve chatted a bit about it before, but would love to hear some updated thoughts.
I generally structure most content as metaobject entries, so having the auto repeater is something I rely on. Makes it kinda tough 100% migrating to theme blocks. Unless I’m missing a better way of handling this?
Just throwing another real world example in here, which is a store list.
Structure:
list.metaobject_reference containing relevant storesVideo showing practical example adding the repeating blocks in the theme editor
Example of generated json:
Other examples could be USPs and FAQs (product/market/region decided).
Also cc @Liam-Shopify, I cant find information in the docs regarding the repeater anymore
In the middle of a Horizon build and just noticed this. There’s no way they just completely ditched repeater blocks on the new architecture without providing an alternative. It’s critical to metaobjects
What’s more, the repeater feature is currently buggy. When connecting a dynamic source, all block settings not associated with a dynamic value vanish away. This can be fixed if you mess directly with the json file settings somehow.
I reported this more than a month ago, they did nothing about it. Reported it once more recently, every single time support is super incompetent and blame it on the theme despite evidences. Basically need to explain to them how the theme editor works 
And as other previously said, they skipped this feature in the new theme architecture. Seems like a half-baked release as we often see with Shopify unfortunately (missing blog articles metafields references are another very frustrating example).
@Liam-Shopify If I may, we need a new block property to detect when a block is a repeater in liquid, such as {{ block.is_repeater }}.
It’s especially needed now since the introduction of visible_if for schema settings. Meaning the repeater could be filling hidden properties, and we might introduce different logic when a block is a repeater.
One example:
A schema setting of type select where the user chooses the type of media he wants to pick: img_picker or video. In the schema settings, for clarity we only show either img_picker or video setting, whichever is selected. We also use the select value in liquid to render either the image or the video element.
But if we use a repeater connected to a Metaobject reference (List) that accepts all files type, the merchant could pick either an image or a video as metaobject entry. In that case, we should update the liquid logic to render the type of media that is not blank, instead of relying on the select value. Do I make sense?
Just adding in here. It seems to be a multi-faceted underlying problem which relates to the repeater functionality, but also to the overall connection of metaobjects to any given section or block where you’ve previously been able to select and use dynamic sources. @MaxDesign we’re seeing the vanishing of settings as well - I just created a case on this using Dawn (not that the client uses it, but to bypass any -contact the theme developer- clutter) - where it happens as well.
Both the lack of repeater possibilities as well as dynamic source connection to blocks and sections is an absolute pivotal part of applying metaobjects to themes and while I realize that metaobjects were mainly introduced due to headless, a lot of us have been using it.
I have a client who can not update their theme and can’t edit crucial parts of their store due to the potential explosion of manual work this would bring going forward.
This needs addressing for sure.
Agree on the two most recent posts – there’s definitely some weird stuff going on with settings simply vanishing after adding a dynamic source. Sometimes it’s even settings that should have been used and should have been able to auto-connect via the added source.
> …is an absolutely pivotal part of applying metaobjects to themes…
