oltdev

<p>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.</p>
<h4>Basic Usage</h4>
<pre><code>[cf "custom field name"]
</code></pre>
<p>Example:</p>
<pre><code>Picture of the day:
<img src='[cf "picture-link"]' />
</code></pre>
<p>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!</p>
<h4>Default Values</h4>
<pre><code>[cf "custom field name" default="display this if the CF is undefined"]
</code></pre>
<p>Example:</p>
<pre><code>Contact [cf "support-email" default="support@mycompany.com"] if you have questions.
</code></pre>
<p>support@mycompany.com will be displayed there if the custom field “support-email” is not present in that post/page.</p>
<h4>Simple Template</h4>
<pre><code>[cf "custom field name" default="default value"]...template...[/cf]
</code></pre>
<p>Example:</p>
<pre><code>Price: [cf "price" default="Pricing information not available yet."] USD$%value% [/cf]
</code></pre>
<p>If you cannot use <code>%value%</code> as your placeholder text for some reason, you can change it by specifying the placeholder attribute.</p>
<p>Example:</p>
<pre><code>Price: [cf "price" default="Pricing information not available yet." placeholder="__value__"] USD$__value__ [/cf]
</code></pre>
<h4>Multiple Values</h4>
<p>It’s smart enough to do the right thing. If your post has the following custom fields:</p>
<ul>
<li>concert-date: Jan 14th</li>
<li>concert-date: Jan 28th</li>
<li>concert-date: Feb 2nd</li>
</ul>
<p>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 (,).</p>
<p>Example:</p>
<pre><code>Come to one of our concerts on the following dates: [cf "concert-date" separator=" / "]
</code></pre>
<p>(=> Jan 14th / Jan 28th / Feb 2nd)</p>
<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>
<p>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>).</p>
<h4>Display Single Value</h4>
<p>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>.</p>
<h4>Summary</h4>
<p>Syntax for <code>[cf]</code> shortcode: (default values in parenthesis)</p>
<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>
<p>Conditionals tags is what makes this plugin unique. Here is a list of them:</p>
<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>
<p>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.</p>
<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>
<p><strong>Please note: It seems that there is a serious bug in WordPress’ shortcode parser that prevents shortcodes from functioning correctly in certain occasions.</strong> 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)</p>


Conditional Custom Fields Shortcode

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

geomagas

<p>This plugin provides an [if] shortcode to conditionally render content. The syntax is the following:</p>
<pre><code>[if condition1 condition2=false condition3]{content}[/if]
</code></pre>
<p>Conditions are passed as attribute names. Multiple conditions evaluate to the result of ORing all of them. In other words, if at least one condition evaluates to the desired boolean result, {content} is rendered, otherwise it is discarded.<br />
Attribute values determine if we want the condition to be true or false. A value of <code>'0'</code>, <code>'false'</code>, <code>''</code> (the empty string), <code>'null'</code> or <code>'no'</code> means we expect the condition to be false. Anything else, including the absense of a value, is interpreted as true.</p>
<p>For example, suppose that we want to include a sentence in a post, but only for anonymous visitors:</p>
<pre><code>[if is_user_logged_in=no]The Sentence.[/if]
</code></pre>
<p>It also provides an [else] shortcode and an [eitherway] one for use inside [if] blocks. [else] will render its content if the condition evaluates to false, and [eitherway] will render its content regardless of the evaluation result.<br />
When used outside an [if] block, these shortcodes behave as if the whole content is surrounded by an [if] shortcode whose condition evaluates to true. In other words, an [else] shortcode would not render any content, while a [eitherway] one would. You can use as many of these shortcodes as you like in a single [if] block, which gives you the ability to do things like:</p>
<pre><code>    - Am I logged in?
    [if is_user_logged_in]- Yes you are.
    [else]- No you are not.
    [/else][eitherway]- I'm sorry, what?
    [/eitherway]- I said YOU A-R-E LOGGED IN!!!
    [else]- YOU ARE NOT LOGGED IN!!! What's the matter with you?[/else][/if]
</code></pre>
<p>A multitude of conditions are supported out-of-the-box. The following evaluate to the result of the corresponding <a href="https://developer.wordpress.org/themes/basics/conditional-tags/" rel="nofollow ugc">WordPress Conditional Tag</a>, using the no-parameter syntax:</p>
<pre><code>    is_single
    is_singular
    is_page
    is_home
    is_front_page
    is_privacy_policy
    is_attachment
    is_category
    is_tag
    is_tax
    is_author
    is_archive
    is_year
    is_month
    is_date
    is_day
    is_time
    is_feed
    is_search
    is_sticky
    is_preview
    has_term
    has_excerpt
    comments_open
    pings_open
    is_404
    is_user_logged_in
    is_super_admin
    is_multi_author
    is_multisite
    is_main_site
    is_child_theme
</code></pre>
<p>For example, the evaluation of the <code>is_page</code> condition is equivalent to calling <code>is_page()</code> with no parameter.</p>
<h3>Extending</h3>
<p>The functionality of the plugin can be extended by other plugins, by means of adding custom conditions through filters. To add a custom condition, a filter hook must be defined in the following manner:</p>
<pre><code>add_filter($if_shortcode_filter_prefix.'my_condition','my_condition_evaluator');

function my_condition_evaluator($value) {
    $evaluate=.... /* add your evaluation code here */
    return $evaluate;
}
</code></pre>
<p>Then, you can use your custom condition like so:</p>
<pre><code>[if my_condition]{content}[/if]
</code></pre>
<p>A big thanks to M Miller for the <a href="http://wordpress.stackexchange.com/a/123073/39275" rel="nofollow ugc"><code>normalize_empty_atts()</code></a> function.</p>


If Shortcode

This plugin provides an [if] shortcode to conditionally render content.

Conditional Custom Fields Shortcode vs If Shortcode