> For the complete documentation index, see [llms.txt](https://docs.acpt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acpt.io/integrations/gutenberg/repeater-and-flexible-content.md). # Repeater & Flexible Content The Repeater fields block The **ACPT Repeater Loop** block allows you to render Repeater and Flexible Content fields directly inside the Gutenberg editor. It works by defining a template — a single "loop item" — that gets repeated once for every row of data stored in the field. *** ### Requirements * ACPT **2.x** or later * A **Meta Box** with at least one **Repeater** or **Flexible Content** field assigned to a post type * The post type must use the **Gutenberg** editor *** ### Adding the block 1. Open the Gutenberg editor on any post. 2. Click **+** to add a new block and search for **"ACPT Repeater"**. 3. Insert the **ACPT Repeater Loop** block. 4. In the **Inspector Panel** (right sidebar), open **General settings**. 5. Use the **Field** dropdown to select a Repeater or Flexible Content field. 6. For **Flexible Content** fields, an additional **Block** dropdown will appear — select which layout block to render. Once a field is selected, the block will generate a template automatically based on the field's structure. *** ### The loop template The template is the single "row" that ACPT will repeat for each entry in the field. It is built inside the **Repeater Loop Item** inner block, which accepts any Gutenberg block (paragraphs, headings, images, buttons, third-party blocks, etc.). Inside any block within the loop item, you reference field values using **tokens** — placeholders wrapped in double curly braces: ``` {{fieldName}} ``` When the page renders, ACPT replaces each token with the actual value for that row. *** ### Token syntax #### Basic token ``` {{fieldName}} ``` Returns the default rendered output for the field type (e.g. a full `` tag for URL fields, a formatted date for Date fields). *** #### Dot notation — accessing sub-values Many field types store structured data (a URL field stores both a URL and a label, an Image field stores a src, alt, title, etc.). You can target a specific property using **dot notation**: ``` {{fieldName.subKey}} ``` **Examples** ``` {{url.url}} → the raw URL only {{url.label}} → the link label only {{image.src}} → the image src URL {{image.alt}} → the alt text {{image.title}} → the image title {{image.id}} → the attachment ID {{phone.dial}} → the dial code (e.g. +39) {{phone.value}} → the phone number only {{currency.amount}} → the numeric amount {{currency.unit}} → the currency code (e.g. EUR) {{address.address}} → street address only {{address.city}} → city only {{address.country}} → country only {{dateRange.from}} → start date {{dateRange.to}} → end date ``` *** #### Arguments — formatting modifiers Some field types support additional formatting arguments separated by colons: ``` {{fieldName:arg1:arg2}} ``` **Date formatting** ``` {{date:d/m/Y}} → 09/03/2026 {{date:F j, Y}} → March 9, 2026 {{dateTime:Y-m-d:H:i}} → 2026-03-09 14:30 ``` Accepts any valid [PHP date format string](https://www.php.net/manual/en/datetime.format.php). **Number formatting** ``` {{price:2}} → 1234.56 (2 decimal places) {{price:2:,:. }} → 1.234,56 (European format) ``` Arguments: `decimals : decimal_point : thousands_separator` **List fields (Checkbox, Select Multi, List)** ``` {{tags}} → default