Divi Dynamic Content Helper

Overview

Dynamic content is powerful, but it can sometimes return empty results, like a missing custom field, a user profile with incomplete information, or a post without a key detail. That’s where the Dynamic Fallback feature in the Divi Dynamic Content Helper plugin comes in. It allows you to display alternate text when your selected dynamic content is empty or unavailable.

Fallbacks help prevent broken layouts, confusing messages, or blank spaces on your site. Instead, you can provide helpful placeholder text, generic labels, or calls to action that maintain a polished and user-friendly experience.

The Dynamic Fallback feature is supported in both of our powerful features, Global Dynamic Content Sources where you select the fallback value in a dedicated input field, and in Dynamic Inline Variables where you add the fallback value directly inside the variable. Let’s take a closer look at how it works in both cases, with real-world examples that show when and why to use fallback values.

How To Use

To start using the Dynamic Fallback Value feature, go to the Pee-Aye Creative menu in your WordPress backend, then select Divi Dynamic Content Helper. In the plugin settings interface, open the Fallback Value tab from the left sidebar.

From there, enable the main feature setting, and the feature will be activated in the Global Dynamic Content Sources feature in the Divi Builder. Now every dynamic content field that supports text will include an optional Fallback input field.

Enabling this setting also activates the feature for our Dynamic Inline Variables, allowing you to define a fallback by appending the tag ‘fallback:‘ followed by your desired text at the end of the variable.

Please note that this fallback value will only appear if the selected content is empty. You might be dynamically pulling in a user’s name, a custom field from a post, or a setting from the site, and if that content isn’t set or available, the fallback gives you a safety net.

Example Use Cases

Global Dynamic Content Sources

Fallback values are a great way to ensure your content always looks polished, even when dynamic sources are empty or missing. For Global Dynamic Content Sources, you can provide friendly defaults that keep your site professional and user-friendly. For example, displaying a user’s full name with a fallback of “Valued Customer” ensures that greetings remain personal even if the user data is unavailable.

Similarly, you can pull in product-specific information like a sale end date and display a fallback such as “While supplies last,” keeping promotional messages clear and consistent. Custom fields, like a call-to-action label, can also use fallbacks like “Learn more,” so your buttons and links always have meaningful text, regardless of missing content.

Display a user’s full name, fallback to “Valued Customer”

• Content Source: Current User
• Content Type: First & Last Name
• Fallback: “Valued Customer”

Pull in a product’s sale end date, fallback to “While supplies last”

• Content Source: Specific Post (Product)
• Content Type: Sale End Date
• Fallback: “While supplies last”

Custom call-to-action label, fallback to “Learn more”

• Content Source: Specific Post
• Content Type: Custom Field (e.g., cta_label)
• Fallback: “Learn more”

Dynamic Inline Variables

For Dynamic Inline Variables, fallback values make inline content flexible and reliable. You can greet a visitor by first name, with a fallback like “there” if the user’s first name isn’t available. Team member information, such as a role or email, can also fall back to a generic label or prompt, ensuring your templates always display sensible content even when specific fields are empty.

These use cases show how fallback values can prevent awkward blanks, maintain consistent messaging, and improve the overall user experience on dynamic, content-rich pages.

Greeting with the user’s first name, fallback to a friendly general term

• Hello, {ddch_current_user:first_name:fallback:there}!

Team member’s role or job title, fallback to a generic label

• {ddch_current_post:custom_field_job_title:fallback:Team Member}

Contact information for a team member, fallback to a general prompt

• {ddch_current_post_author:email:fallback:Email us for more info}