| 开发者 | artemsemkin |
|---|---|
| 更新时间 | 2026年7月13日 04:39 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
Yes, with Elementor Pro: enable "Repeat by ACF Repeater" on a Loop Grid or Loop Carousel and bind the loop template's tags to "Current loop row" — one card per row, across every queried post. Pagination counts posts, not cards, so a page can show more cards than the "posts per page" number. While editing the loop template itself, the card previews the first row of the template's "Preview Dynamic Content as" post — point it at a post that has rows to see real values instead of placeholders. On free Elementor (which has no loop widgets) each tag reads one addressed row: any index, or "Last row".
No. Everything runs on free Elementor 3.5 or newer. With Pro on top you get Theme Builder templates, repeat mode on the Loop Grid and Loop Carousel, and the row count display condition.
You need a plugin that provides the repeater field type: ACF Pro, or Secure Custom Fields — the free fork on WordPress.org that includes repeaters and options pages. Both work identically here. With free ACF (no repeaters) the picker has nothing to list.
Rows are read from the current context: the post you're editing, or whatever "Preview Dynamic Content as" points to in a Theme Builder template — a post, or the term of a taxonomy archive. If that target has no saved rows there's nothing to pick, and on the frontend the tag renders empty where rows are missing. Add rows to the previewed target or switch the preview to one that has them.
Addressing is positional. A tag pointing at row 2 shows whatever currently sits in row 2, not what was there when you picked it. "Last row" always follows the final row. ACF rows have no stable IDs, so pinning a row by its content isn't possible.
Yes, one level deep. Group sub-fields appear in the sub-field dropdown as "Group → Field" paths. A repeater inside a repeater gets a second row picker: pick the parent row, then the nested row — any index, or "Last row". Flexible content fields work like repeaters whose row picker labels each row with its layout; if a row's layout doesn't include the chosen field, the tag renders empty for that row instead of guessing. It also works in reverse: a repeater or flexible content field sitting inside a top-level group shows up in the repeater picker as its own entry. Deeper nesting isn't supported.
oEmbed (store the URL in a URL sub-field instead), true/false, password, icon picker, and clone fields. Structures nested deeper than one level are out too.
Taxonomy term and author archives work; the tag reads the repeater from the queried term or user. A custom post type archive has no single post to read from, so tags there fall back to the first post of the archive's main query. The editor previews them against the newest post of that type — the same post on a date-sorted archive, a different one under a custom sort order or on later pages.