Documentation-based practice example; check the controls in your installed Oxygen version.
What it does and when to use it
Display the rows of a supported ACF repeater field. This example focuses on one achievable outcome rather than listing every possible setting.
Before you start
Start with a test page and the data or assets described in the example. The values below are starting points, not universal design defaults.
Worked example: A project specification list from ACF
Scenario: A project specification list from ACF. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Create an ACF repeater with label and value subfields, using an ACF edition that supports repeaters.
- Enter three rows on a project post, such as Platform / WordPress and Builder / Oxygen.
- Select the repeater source and a repeated Component bound to the row subfields; preview that project and a second project with no rows.
Example repeater data
Project facts
Row 1: label = Platform; value = WordPress
Row 2: label = Builder; value = Oxygen 6
Row 3: label = Content; value = Guides and toolsCreate label and value as subfields in your supported ACF repeater. These are field labels and example values, not a shortcode to paste into Oxygen.
Expected result
You should have a project specification list from ACF. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.
Troubleshooting
If rows are empty, check the selected field, post preview context and subfield bindings. Use a post loop for separate posts; a repeater loops rows stored on one object.
Checks before publishing
This needs the appropriate custom-field integration and data. A post loop and a field repeater solve different problems.
- Compare desktop and narrow-screen layouts using actual content.
- Follow every destination and operate interactive controls with a keyboard where applicable.
- Check an empty or unavailable-data state when the element depends on a provider.
Official reference and version notes
Official Repeater Field reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.
The native references were checked against the site’s Oxygen 6.2.0-beta.9 installation and public documentation. Individual recipes should still be validated in your project.