Your Cart
Elementor dynamic content custom post types

How to Use Elementor Dynamic Content with Custom Post Types and Custom Fields

When several entries on a WordPress website share the same structure, creating each page separately can make content management unnecessarily repetitive. Elementor dynamic content provides a way to connect a reusable layout with information stored in the current WordPress post, page, or custom post type. The template remains consistent, while displayed values can change for each entry.

This approach is useful when a custom post type contains repeated records and additional information is stored in custom fields. Elementor documents support for custom post types, custom fields, and integrations with ACF, Toolset Types, and Pods. The exact result still depends on the selected widget, field type, template settings, and the integrations available in the installation. Dynamic Tags are documented as an Elementor Pro feature.

What Elementor Dynamic Content Means for Custom Post Types

Elementor dynamic content connects a template field with data from the current WordPress entry. Instead of entering one fixed value into every layout, you select a dynamic source. When the template is viewed for another custom post type entry, Elementor can retrieve the corresponding value from that entry.

The custom post type defines the type of content being presented. Custom fields store additional information associated with its entries. Together, they allow one reusable layout to represent multiple entries without manually rebuilding the same design each time.

Reusable layouts and changing entry values

A reusable template may contain a title, descriptive text, image, or link whose value comes from the current entry. The layout itself does not need to be duplicated for every record. If the underlying content changes, the displayed dynamic value can change as well. This is the central difference between a fixed Elementor value and a value connected to the current post or custom post type.

This workflow should be treated as a documented configuration model, not as a guarantee that every custom post type or third-party field system will behave identically. Confirm the available dynamic source and the returned output in the actual site before publishing.

What You Need Before Building the Template

Begin with a registered custom post type and entries containing the information that the template should display. If the layout requires additional data, create the relevant custom fields through a supported field solution. Elementor documents integrations with Advanced Custom Fields, Toolset Types, and Pods. These documented integrations do not establish universal compatibility across every plugin version, field configuration, or return format.

Use populated entries while previewing the design. Empty fields can make a correctly configured template appear incomplete, while an unexpected field type can produce output that does not suit the selected widget. Decide in advance whether the design belongs to an individual entry or to an archive context.

Single Post versus Archive scope

Use a Single Post template when the design should apply to an individual custom post type entry. Use an Archive Template when the design should apply to the custom post type archive or listing context. In both cases, configure display conditions so Elementor knows where the template should apply.

Keep these scopes separate during setup. A field-display problem is different from an archive-availability problem, and troubleshooting becomes clearer when the intended template type is known first.

How to Display Custom Fields in Elementor

The documented workflow starts in the relevant Elementor template. Open the Single Post or other appropriate template in Theme Builder, then select a widget whose field should receive the dynamic value. The dynamic control belongs to a supported input, so do not assume that every widget exposes identical controls.

After selecting the widget, open the Dynamic Tags control beside the relevant input. Choose the post or custom-field source that corresponds to the field system used on the site. Depending on the available integration, this may include an ACF field, Pods field, or post custom-field source. Select the exact field key, then preview the result with an entry that contains a value.

  1. Open the relevant Single Post or other Elementor template.
  2. Select the widget and identify the input that should display the field.
  3. Open the Dynamic Tags control beside that supported input.
  4. Choose the available source for the field system used on the site.
  5. Select the exact field key and inspect the rendered result.
  6. Test the output before publishing, especially for URLs, images, dates, and user-entered text.

Testing matters because the same general workflow may produce different practical results depending on the widget and field type. Verify that text appears as expected, that an image field supplies a usable image value, and that a link-related value behaves correctly in the selected input. Make template changes on a staging or backup copy when possible.

Connecting the field key to a widget input

Select the widget first rather than choosing a field source in isolation. Then match the source to the field system used by the site and select the exact key. Preview the template with populated custom post type content. If the value is missing, check the key, the entry data, the selected source, and the expected field type before changing other parts of the layout.

Choosing Widgets for Dynamic Values

Elementor’s documented custom post type and custom-field workflow gives several common widget examples. Heading can be used for a dynamic text value, while Text Editor can present dynamic text content. Image is a documented example for image-related content, and Button is a documented example when a dynamic value is used in a button field.

These examples should not be read as a complete compatibility matrix. The reviewed documentation does not establish that every Elementor widget supports every custom-field type or return format. Validate the specific combination in the installation before relying on it in a published template.

Match the widget to the returned value

Use a text-oriented widget when the available dynamic source returns text suitable for that input. For Image, verify that the selected field and returned value work with the image input. For Button, test the dynamic link value and the resulting destination before publishing. The field type, widget input, and integration should be considered together rather than independently.

If a source is not available beside the input, do not infer universal incompatibility from one configuration alone. First confirm that the widget, field system, field key, and active Elementor configuration are the intended ones.

Creating Single and Archive Templates for Custom Post Types

Build a Single Post template when one design should control the presentation of individual custom post type entries. Build an Archive Template when the design should apply to the archive context for that custom post type. After designing the layout and connecting dynamic fields, configure display conditions for the intended content.

Display conditions determine where Elementor applies the template. Review them after saving and test with a real entry. For archive work, also verify the custom post type configuration described in Elementor documentation. The archive setting is a separate consideration from the dynamic field connection.

Display conditions and archive availability

When an Archive Template does not apply to a custom post type, check that the post type’s Has Archive setting is enabled, as described in Elementor’s documentation. Then review the display conditions and confirm that the tested URL represents the archive context targeted by the template.

For a Single Post template, confirm that the conditions target the intended custom post type. Test with more than one populated entry where possible, because a reusable layout should retrieve values from the current entry rather than display only the data used during editing.

Troubleshooting When the Template Does Not Load

A custom post type template that does not appear may have a configuration problem separate from the field itself. Start with the template type and display conditions, then check the page-template settings used by the affected entry. Elementor documents several specific checks for Single Page Templates and archive templates.

Single template overrides and missing content

For a Single Post template, check that the affected entry uses the Default page-template setting. Elementor explains that a Single Page Template can override the relevant theme PHP template, while Elementor Full Width or Elementor Canvas settings can override the Single Page Template. These settings can therefore explain why an apparently correct template is not being applied.

When editing a Single Page Template, confirm that the Post Content widget is present where required. Elementor documents that this widget retrieves content created in the WordPress editor, and its absence can produce a “The Content” error. This check concerns the template’s content structure; it is distinct from connecting a custom field to a widget through Dynamic Tags.

A controlled testing sequence

Use a controlled sequence rather than changing several settings at once. First review display conditions. Next check whether the custom post type has the required archive setting when working with an Archive Template. For a Single Post template, verify the Default page-template setting and check for Full Width or Canvas overrides. Then confirm that the required Post Content widget is present.

If the documented checks do not explain the result, treat theme behavior, plugin conflicts, caching, permissions, and custom-field configuration as site-specific diagnostic possibilities, not confirmed causes. Do not begin by disabling security, caching, or production plugins. If conflict testing is necessary, use a staging environment, change one configuration at a time, and keep a documented rollback plan.

Before publishing, review the output with populated entries and confirm that the intended template is used for both the page context and the field values. A successful preview of one entry does not by itself establish universal compatibility for every entry, field type, widget, or third-party integration.

In practice, the workflow is straightforward: prepare the custom post type and its fields, choose between a Single Post and Archive Template, configure display conditions, and connect supported widget inputs through Dynamic Tags. Heading, Text Editor, Image, and Button are documented examples, but the actual widget and field combination should be verified in the installation. When a template does not load, check archive availability, page-template overrides, display conditions, and the required Post Content widget before investigating site-specific causes. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń