oltdev

A series of shortcodes for using custom field values in pages or posts (or in sidebar widgets – via <a href="https://wordpress.org/extend/plugins/widget-logic/" rel="ugc">Section Widget</a>!), which would then allows you to take store the actual data in custom fields while storing the presentation in the page/post body. This transforms WordPress into an awesome CMS. Keep reading for more inspirations.
<h4>Basic Usage</h4>
<pre><code>[cf "custom field name"]
</code></pre>
Example:
<pre><code>Picture of the day:
<img src='[cf "picture-link"]' />
</code></pre>
This would output something like <code><img src='http://thesite.com/something.jpg' /></code>, assume the post/page has the custom field “picture-link” and its value is “http://thesite.com/something.jpg”. That way, you (or your clients!) would never accidentally take out a div when updating your page because you won’t have to touch the page/post body anymore!
<h4>Default Values</h4>
<pre><code>[cf "custom field name" default="display this if the CF is undefined"]
</code></pre>
Example:
<pre><code>Contact [cf "support-email" default="support@mycompany.com"] if you have questions.
</code></pre>
support@mycompany.com will be displayed there if the custom field “support-email” is not present in that post/page.
<h4>Simple Template</h4>
<pre><code>[cf "custom field name" default="default value"]...template...[/cf]
</code></pre>
Example:
<pre><code>Price: [cf "price" default="Pricing information not available yet."] USD$%value% [/cf]
</code></pre>
If you cannot use <code>%value%</code> as your placeholder text for some reason, you can change it by specifying the placeholder attribute.
Example:
<pre><code>Price: [cf "price" default="Pricing information not available yet." placeholder="__value__"] USD$__value__ [/cf]
</code></pre>
<h4>Multiple Values</h4>
It’s smart enough to do the right thing. If your post has the following custom fields:
<ul>
<li>concert-date: Jan 14th</li>
<li>concert-date: Jan 28th</li>
<li>concert-date: Feb 2nd</li>
</ul>
Then <code>[cf "concert-date"]</code> will output <code>Jan 14th,Jan 28th,Feb2nd</code>, exactly what you would expect. You can also optionally provide a separator to replace the default (,).
Example:
<pre><code>Come to one of our concerts on the following dates: [cf "concert-date" separator=" / "]
</code></pre>
(=> Jan 14th / Jan 28th / Feb 2nd)
<h4>Sorting</h4>
<pre><code>[cf "custom field name" sort="nosort|asc|dsc|random" type="string|int|integer|float|bool|boolean|date|auto"]
</code></pre>
You can control how it sort the items (when there’s more than one) using the sort attribute (default is <code>nosort</code>). By default, it would compare them using PHP’s comparison operator (i.e. try to cast them into numeric values, or compare them as strings if that failed). However, you can force a type cast by specifying the type attribute (default is <code>auto</code>).
<h4>Display Single Value</h4>
If display multiple values is not what you want it to do, you can use <code>[cf single="true"]</code> to force it to display only the first value. Combining what we have learned so far, you can display a single random value by <code>[cf single="true" sort="random"]</code>.
<h4>Summary</h4>
Syntax for <code>[cf]</code> shortcode: (default values in parenthesis)
<pre><code>[cf "field-name" default="" placeholder="%value%" single="(false)|true" separator="," sort="(nosort)|asc|dsc|random" type="string|int|integer|float|bool|boolean|date|(auto)"](OPTIONAL) template[/cf]
</code></pre>
<h4>Conditionals</h4>
Conditionals tags is what makes this plugin unique. Here is a list of them:
<pre><code>[if-cf-def "custom field name"]
 Do this when "custom field name" is defined for this page/post
[/if-cf-def]

[if-cf-ndef "custom field name"]
 Do this when "custom field name" is NOT defined for this page/post
[/if-cf-ndef]

[if-cf-eq "custom field name" "value"]
 Do this when "custom field name" == "value"
[/if-cf-eq]

[if-cf-neq "custom field name" "value"]
 Do this when "custom field name" != "value"
[/if-cf-neq]

[if-cf-lt "custom field name" "value"]
 Do this when "custom field name" < "value"
[/if-cf-lt]

[if-cf-gt "custom field name" "value"]
 Do this when "custom field name" > "value"
[/if-cf-gt]

[if-cf-let "custom field name" "value"]
 Do this when "custom field name" <= "value"
[/if-cf-let]

[if-cf-get "custom field name" "value"]
 Do this when "custom field name" >= "value"
[/if-cf-get]
</code></pre>
More detailed documentations will be published soon. In the mean time, check out the following examples and the comments in the PHP code to get a rough idea.
<h4>Examples</h4>
<pre><code>[if-cf-get "deadline" "today" type="date"]
 Submit your application <a href='[cf "submit-link"]'>here</a>.
[/if-cf-get]

[if-cf-lt "deadline" "today" type="date"]
 Sorry we regret that we cannot take anymore applications.
[/if-cf-lt]

[if-cf-def "discounted-price" "discount-expires" logic="and"]
 This product is on discount, get it now for [cf "discounted-price" /] [cf "discount-expires" default="for a limited time"]before %value%[/cf]!
[/if-cf-def]
</code></pre>
Please note: It seems that there is a serious bug in WordPress’ shortcode parser that prevents shortcodes from functioning correctly in certain occasions. The developers are hard at work to get this fixed before the 2.8.3 release. (See <a href="https://core.trac.wordpress.org/ticket/10082" rel="nofollow ugc">#10082</a>) Therefore, please do not report any parser related bugs for the moment. (e.g. the shortcode is displayed on the actual page)

Conditional Custom Fields Shortcode

Use custom field values in you pages or posts. With conditional supports which enables basic templating with custom fields.

dudaster

Ele Conditions for Elementor turns static Elementor elements into interactive, context-aware components — without writing a single line of code.
There are two independent systems, both accessible from the Advanced tab of any widget, section, or container:
<h4>⚡ Triggers & Actions (client-side, no page reload)</h4>
Attach one or more trigger → action pairs to any element.
10 trigger types:
<ul>
<li>Click — user clicks the element</li>
<li>Hover — user hovers over the element</li>
<li>Delay on load — fires after X milliseconds from page load</li>
<li>Scroll into view — fires once when the element enters the viewport</li>
<li>Time on page — fires after X seconds the visitor has been on the page</li>
<li>Exit intent — fires when the cursor moves toward closing the tab</li>
<li>First visit — fires only on the visitor’s very first page load (localStorage)</li>
<li>Nth visit — fires on the Nth page load (visit counter in localStorage)</li>
<li>A/B Group A / B — fires for visitors randomly assigned to group A or B (persists via localStorage)</li>
</ul>
9 action types:
<ul>
<li>Show — make the target element visible</li>
<li>Hide — hide the target element</li>
<li>Toggle — toggle visibility on each trigger</li>
<li>Add / Remove / Toggle Class — apply a CSS class (great for CSS animations)</li>
<li>Scroll To — smooth-scroll the page to the target element</li>
<li>Focus — set browser focus on the target (input fields, etc.)</li>
<li>Close Others in Group — hide all siblings sharing a CSS class (accordion pattern)</li>
</ul>
Target selector: leave empty to act on the element itself, or enter any CSS selector to act on another element anywhere on the page.
Hide Initially: a dedicated switcher that hides the element on load independently of triggers — useful for elements revealed by a trigger.
<h4>🎛 Display Conditions (server-side, evaluated at render time)</h4>
Show or hide elements based on variables, rules, and time windows. Multiple conditions per element with AND / OR logic.
Built-in variables include: <code>user_role</code>, <code>is_logged_in</code>, <code>user_id</code>, <code>post_type</code>, <code>post_status</code>, <code>post_age_days</code>, <code>post_word_count</code>, <code>post_has_thumbnail</code>, <code>cart_count</code>, <code>cart_total</code>, <code>current_hour</code>, <code>current_day</code>, <code>current_month</code>, <code>current_year</code>, <code>utm_source</code>, <code>utm_medium</code>, <code>utm_campaign</code>, <code>utm_content</code>, <code>utm_term</code>, and more.
Condition types:
<ul>
<li>Simple — compare a variable to a value using ==, !=, >, <, >=, <=, contains, starts_with, ends_with, empty, not_empty</li>
<li>Time interval — show element only between two times of day (supports cross-midnight ranges)</li>
<li>Date/datetime interval — show element only within a date or datetime window</li>
</ul>
Custom variables — register your own variables via the <code>eleconditions_vars</code> filter in your theme’s <code>functions.php</code>.
ACF support — pick any ACF field from a searchable dropdown; the value is fetched at render time.
User meta — condition on any WordPress user meta key for the current visitor.
Debug mode — shows a red-bordered overlay with the evaluated variable values, visible only to editors and administrators.
<h4>Developer-friendly</h4>
<ul>
<li>Zero dependencies beyond Elementor</li>
<li>Fully filterable variable system</li>
<li>No inline styles injected into saved content — everything is evaluated at render</li>
</ul>
Note: Requires the free <a href="https://wordpress.org/plugins/elementor/" rel="ugc">Elementor</a> plugin.

Ele Conditions for Elementor

Add interactive triggers and conditional display logic to any Elementor element — show, hide, toggle on click, scroll, exit intent, and more.

Conditional Custom Fields Shortcode vs Ele Conditions for Elementor