A repeater with twelve rows was forty-eight input fields stacked on top of each other. You could never see more than two or three rows at once, you lost track of where you were in the list, and dragging a row to a new position meant dragging it somewhere off screen. Twelve rows is modest; a FAQ or a price list on a client site reaches thirty without trying.
- A repeater can point at one of its own sub fields to act as the row label. Rows that have a value for it open collapsed, so twelve rows read as twelve lines and you click open the one you need. Measured on the same three-row repeater, the editing screen went from 343 pixels to 175.
- The heading follows what you type. It is already right before you save, which matters because the label is how you find the row again.
- A row with nothing in that field stays open. That one rule does three jobs at once: a row you just added does not fold itself away before you have filled anything in, an empty row never becomes a blank bar you have to click to discover there is nothing behind it, and a repeater on a public form behaves exactly as it did, because every row there starts empty.
- Choice fields show the label you picked, not the key stored behind it. A select that stores
nlwhile you choseNederlandwould putnlon the heading, which is precisely the result this setting exists to prevent. - Only sub fields that produce a readable line can be chosen. Checkboxes, images, files and dates are not offered, because
1, an attachment ID and20180315are not labels. That rule is now enforced on the server too, not only in the builder, so a field group registered in PHP or imported from elsewhere cannot slip past it.
Leave the setting empty and nothing about your repeaters changes. That is checked on every release against 450 combinations of layout, sub field types, row values and settings, compared byte for byte with the previous implementation.