Repeater2Template Widget for ACF Repeater and Elementor vs WPGraphQL for ACF

⚠️ Requires Elementor Pro Tired of ACF Repeater fields that won’t cooperate with Elementor? Repeater2Template fixes that — instantly. Connect any repeater data source to any Elementor template and watch every row render exactly how you designed it. No PHP. No shortcodes. No workarounds. Whether you’re working with ACF Repeater fields, a raw JSON array, or a live API endpoint — this widget loops through your data and outputs each item using your own Elementor saved template. Full design control, fully native experience. 🎥 See It In Action: 💡 Key Features 🔌 3 data sources, one widget — ACF Repeater, JSON Array, or live data from any JSON URL / API. 🎨 Design freedom — pick any Elementor Pro saved template to render each row your way. 🗂 Flexible ACF sources — current post, any specific post by ID, or a global ACF Options Page. 🏷 Subfield-to-dynamic-tag mapping — keeps your templates clean, reusable, and truly dynamic. 🌐 Live API rendering — inject dynamic parameters into JSON URLs for real-time, context-aware content. 🔢 Row limit control — display only a set number of items from any data source. ✅ 100% no-code — built entirely inside Elementor. If you can drag a widget, you can use this. 🔁 Flexible ACF Data Sources Real-world projects rarely keep all data tied to the current post. That’s why Repeater2Template supports three ACF source types: Current Post → repeater data tied to the page being viewed. Specific Post (by ID) → use any post as a centralized “data hub” — reuse it across unlimited templates without duplication. Options Page → pull from any registered ACF Options Page for global content like team sections, banners, menus, or footers. Centralize once. Reuse everywhere. 🌐 JSON Array & JSON URL — No ACF Needed Not an ACF user? No problem. Repeater2Template handles raw JSON just as powerfully. Two JSON modes: JSON Array — paste your data directly into the widget. Instant, portable, zero setup. [ { “title”: “Book A”, “author”: “Author X”, “image”: “https://example.com/book1.jpg” }, { “title”: “Book B”, “author”: “Author Y”, “image”: “https://example.com/book2.jpg” } ] JSON URL — fetch live data from any internal or external API endpoint. Supports dynamic URL parameters (post ID, category, user meta, and more). Perfect for product feeds, API-driven testimonials, blog lists, or user-specific content. The plugin parses the response automatically and renders each object using your Elementor template. Example: https://api.example.com/books?category=fiction&user_id={{user_id}} ⭐ What Builders Are Saying “Extremely simple and yet so powerful!” — davidedev “Saves tons of time and just works — super intuitive!” — akhileshtenguriya “This is literally a gem. All must try this.” — mairaaah “The support went the extra mile. Excellent plugin.” — indyparker 5 out of 5 stars — every single review. How It Works Step 1: Design Your Item Template Go to Templates → Saved Templates → Add New. Choose Section or Container. Design one item — a team card, a testimonial block, a product tile, anything. Save the template. Step 2: Drop In the Widget Open your page in Elementor. Search for Repeater2Template and drag it onto the canvas. Select your data source: ACF Repeater — pick your field by key or name. JSON URL / Array — paste your JSON or enter a URL. Step 3: Connect & Done Select the Elementor template from Step 1. The widget loops through every item and renders each one using your template — automatically. No PHP. No shortcodes. No headaches.

WPGraphQL for Advanced Custom Fields is a free, open-source WordPress plugin that adds ACF Fields and Field Groups to the WPGraphQL Schema. Create ACF Field Groups Create ACF Field Groups and Fields using the ACF User Interface, register them with PHP, or leverage ACF local JSON. Each field group and the fields within it can be configured to “Show in GraphQL.” Query your fields with GraphQL Once your field groups and fields are configured to “Show in GraphQL,” they become available in the GraphQL Schema for querying. Supported Field Types WPGraphQL for ACF provides support for most built-in field types of ACF (free & PRO) and extends support to most field types from ACF Extended (free & PRO). Updating If you are updating from WPGraphQL for ACF v0.6.* or older, check out the Upgrade Guide For non-major version updates, automatic updates usually should work smoothly, but we still recommend you back up your site and test on a staging site. Before updating WPGraphQL for ACF, review the release notes on GitHub. We follow Semantic Versioning (Semver) for meaningful releases: MAJOR version for incompatible API changes, MINOR version for backwards-compatible functionality additions, PATCH version for backwards-compatible bug fixes. Learn more about Semver at semver.org. Support General Help Requests: For general questions and help requests, create a new topic in Github Discussions Discord Community: The WPGraphQL Discord is a great place to communicate in real-time. Ask questions, discuss features, get to know other folks using WPGraphQL. Bug Reports: Report a bug in WPGraphQL Feature Requests: Suggest an idea, feature, or enhancement for WPGraphQL. Report a Security Vulnerability: Report a security vulnerability. FAQs Does this work with ACF Extended? Yes! WPGraphQL for ACF allows you to query for (most) fields created with ACF Extended. Can I filter and sort queries by ACF Fields using WPGraphQL for ACF? At this time WPGraphQL for ACF does not support filtering or sorting queries by ACF Fields. “Meta Queries” are often very expensive to execute, so we currently do not support filtering by ACF fields out of the box, but are exploring options for supporting it without the performance penalty. I think I found a bug, where do I report it? If you think you found a bug, please open an issue on GitHub. The more details you provide in the issue, and the more clear your steps to reproduce are, the higher chances we will be able to help. Can I use ACF Free or Pro with WPGraphQL for ACF? Yes! WPGraphQL for ACF works great with ACF Free and Pro. The Pro version of ACF has some additional features, such as Flexible Content Fields, Repeater Fields and Options Pages that are supported by WPGraphQL for ACF. Do I have to use Faust.js to use WPGraphQL for ACF? No! You can use WPGraphQL for ACF with any GraphQL client, including Apollo, Relay, Urql, Faust.js, etc. I have an ACF Extension that adds a new field type, will it work with WPGraphQL for ACF? WPGraphQL for ACF supports the field types that come with ACF (Free and PRO) as well as the field types in ACF Extended (Free and PRO). Support for additional field types can be added by using the “register_graphql_acf_field_type” API. Do I need WPGraphQL and ACF to be active to use this? This plugin is a “bridge” plugin that brings functionality of ACF to WPGraphQL. Both WPGraphQL and ACF need to be installed and active in your WordPress installation for this plugin to work. How much does WPGraphQL for ACF cost? WPGraphQL for ACF is a FREE open-source plugin. The development is sponsored by WP Engine Atlas. Does WPGraphQL for ACF support GraphQL Mutations? GraphQL Mutations are not yet supported. We are working on adding support for Mutations in the future. We are waiting for the GraphQL “@oneOf” directive to be merged into the GraphQL spec before we add support for Mutations. Does this work with Field Groups registered in PHP or JSON? Yes! You can register ACF Field Groups and Fields using the Admin UI, PHP or JSON. WPGraphQL for ACF will detect the Field Groups and Fields and add them to the GraphQL Schema. If using PHP or JSON, you will need to set the “show_in_graphql” setting to “true” to expose the Field Group and Fields to the GraphQL Schema. There might be other settings that need attention at the field group or field level that might impact the schema or field resolution. Privacy Policy WPGraphQL for Advanced Custom Fields uses Appsero SDK to collect telemetry data upon user confirmation, helping us troubleshoot problems and improve the product. The Appsero SDK doesn’t collect data by default and only starts gathering basic telemetry data when a user allows it via the admin notice. No data is collected without user consent. When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below). Learn more about how Appsero collects and uses data.