The Repeater field is an ACF Field Type that provides a simple solution for repeating content – for example, team members, URLs and the like. This field type acts as a parent to a set of Sub Fields which can be repeated again and again. What makes this field type special is its versatility. Any kind of field can be used within a Repeater, and there are no limits to the number of repeats.

The ACF Repeater Sub Fields are used in conjunction with the ACF Repeater. The Sub Fields area defines the set of repeatable sub fields available. In the example below, only one Sub Field has been added. For a working example of how to use ACF Repeater and ACF Repeater Sub Fields together, see the section below on How To Use ACF Repeaters With Parent & Child Elements.

The Relationship field provides a dual-column component to select one or more posts, pages or custom post type items. In the Project Fields Field group on the Programmer Prebuilt, the Client Field field type is set to Relationship, filtered by the Testiomonial Post Type.

Therefore when editing the Single Projects, you get a list of testimonials to choose from for the post.

With Parent & Child Elements, such as the Checklist Element, we use the ACF Repeater & ACF Repeater Sub Field together.

You can find an example of this on any Single Project page on the Programmer prebuilt. Here, in the Single Project Content Layout Section, you can see the URLs section on the right. Here, a Checklist Element has been used to pull values from the URLs Repeater Field, found in the Project Fields Field Group.

In the Checklist Element, the Dynamic Content of ‘ACF Repeater’ has been applied, and set to the URLs field.

Then in the Child Item field, the ‘ACF Repeater Sub Field’ has been added as the dynamic content, with the Sub Field of project_url.

In this way, however many URLs are in the URL Sub Field in each specific project post, would then be repeated on the front end of the post. In this example, there were three URLs added to this specific post.

The ACF Repeater Single Value Dynamic Content allows a single value of the Repeater Sub Fields to be targeted. For example, if you wanted to only pull the first link from the repeater demonstrated above, you could add the Repeater Single Value Dynamic Content into a Text Element, setting the Repeater field name, the Sub Field name, and the value you require. In this example, this would pull the first URL in the Sub Field list.

You can also use ACF Repeaters with Post Cards. Again, as an example, let’s look at how this is used on the Programmer Prebuilt.

Here a Post Card has been designed to pull data pulled from ACF Sub Fields. There is an Icon, a Title and a Text Block Element, all pulling the ACF Repeater Sub Field via Dynamic Content. Each one pulls the relevant Sub Field of Icon, Tile or Description.

Then in the Content Layout Section, in the Project Tasks area, the Post Card has been displayed with the Post Card Element, using the ACF Repeater as the Content Source. The Repeater field of tasks was then chosen, which contains the afforementioned Sub Fields.

In the same way, you can also use ACF Relationship data with Post Cards, Again, in the Programmer Prebuilt, in the Client area of the Content Layout Section, this information is pulled using a Post Card, with ACF Relationship as the Content Source, and client as the Relationship Field.

You can also use conditional rendering in conjunction with the ACF Dynamic Content, to set up advanced Layouts. Let’s look at a few examples.

In the Testimonial Nested Column for example, there is some Conditional Rendering on the Column itself. This uses the ACF Repeater Count to check if there are any clients added to the post. If the number of clients is not greater than 0, the column will not be rendered. You could use the ACF Relationship Count in a similar way.

Another example might include the ACF Repeater Value. Our Project Tasks Layout could be built in an entirely different way, using the ACF Repeater Single Value to pull the icons, titles and descriptions, instead of using a Post Card.

As can be seen in the screenshot below, the Icon is added via the ACF Repeater Single Value, set to the tasks Repeater field, and the Icon Sub Field, with an index of 1 (the first icon). In the same way, the title and description can be set.

Rendering logic could then be used to check if one of the ACF Repeater Single Value is empty (In the example below, it is the Title that is being checked, but it could just as well be the icon or description). If it is, we don’t have any content, and so the column would not be rendered.

The first thing you need to do is to create a new Layout for your Thank You page. To do this, head to the Layout Builder at Avada > Layouts and add a new Layout. You might call it Woo Thank You, or whatever else makes sense to you. At this point, the Layout will be empty.

Now you need to set the conditions for which the Layout will be used. To do this, click on Manage Conditions at the bottom of your newly made Layout, and on the Other page, select WooCommerce Thank You Page as the single condition.

Now it’s time for the content. You can add any Layout Sections you want to this Layout, but the most important one is the Content Layout Section. This is where you will add the Woo Order Elements. So, click on ‘Select Content’ on the Layout and create a new Layout section. Give it a name, and click on Create New Section, and then you can click on the Edit icon to edit the Layout Section. Choose your Avada Builder of choice.

Now comes the fun part – designing your page. Depending on your other Layout Sections and site design, you might want to add a Title Element at the top or not. You can, in fact add any Elements in this Content Layout Section. But the most important Elements to add are the Woo Order Elements, as listed below.

Once you have completed the design of your thank you page, just save your Layout Section, and you’re done. Now just sit back and relax and wait for those orders to come in.

The next time a user purchases something from your store, when they complete checkout, they will be directed to your custom Thank You Page. How’s that for personal service!

If your custom Thank You page does not display when you test it, it’s likely that another layout is interfering. Any other layouts using All Pages or Checkout in the Conditions could potentially do this.

You could go in and exclude the WooCommerce Thank You page from any other layouts using All Pages or checkout, but the easiest way to deal with this is just to move the Thank You Page Layout to the end of the layouts. Apart from the global layout, layouts further down the list take precedence over ones higher up.

So just make sure the Thank You Page layout is further down than any other layouts using All Pages or Checkout in the Conditions, and Save the Layout Order, and there should be no conflict.