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.

Super Interactive

<h4>How to use</h4>
<p>You can place conditional content between <code>if</code> <a href="https://codex.wordpress.org/Shortcode" rel="nofollow ugc">shortcodes</a>, and use its attributes to define conditions. The content between the shortcodes will only be displayed if all defined conditions are met.</p>
<h4>Defining conditions</h4>
<p>Conditions are defined by setting the attributes of the shortcode in the following format:</p>
<pre><code>[if <type>=<condition>]
 Conditional content
[/if]
</code></pre>
<p>A basic example:</p>
<pre><code>[if qs="product-type:shoes"]
 Thank you for buying shoes
[/if]
</code></pre>
<p>The text in this example will only be displayed if the current URL has a GET paramater of “product-type” with the value “shoes”.</p>
<p>Available condition types are:</p>
<ul>
<li>
<p><strong><code>qs</code></strong> – Match on the key/value pair of the defined query string/GET parameter. Query string conditions are formatted like this:</p>
<pre><code>[if qs="<qskey>:<qsvalue>"] … [/if]

qskey is the name of the query string variable and `qsvalue` the value to test for. For example, the condition `qs="product-type:2"` will match `?product-type=2`.
</code></pre>
</li>
<li>
<p><strong><code>referrer</code></strong> – To check on the current referrer. The condition will be true if <code>HTTP_REFERER</code> contains <code><value></code>. The match doesn’t need to be exact, so if a user arrives from google and <code><value></code> is set to “google.com” the condition will be true.</p>
</li>
<li>
<p><strong><code>role</code></strong> – Matches the current user’s role. The match needs to be exact so “admin” will not match “administrator”. Use <code>role</code> with and empty value if you want to match users that are not logged in.</p>
</li>
</ul>
<h4>Examples</h4>
<p>Display content based on query string:</p>
<p>[if qs=”utm_source:partner-site”]<br />
     This content is only displayed if the current URL contains a GET paramater ‘utm_source’ with value ‘partner-site’<br />
    [/if]</p>
<p>Display content based on referrer:</p>
<pre><code>[if referrer="www.google.com"]
 This content is only displayed if the referring URL contains 'www.google.com'
[/if]
</code></pre>
<p>Display content based on user role:</p>
<pre><code>[if role="editor"]
 This content is only displayed if the user is logged in with the role 'editor'
[/if]
</code></pre>
<p>Setting multiple conditions and combining condition types:</p>
<pre><code>[if referrer="www.example.com" qs="utm_source:partner-site"]
 This content is displayed to users coming from example.com who clicked on a link originating from our RSS feed.
[/if]
</code></pre>
<h4>Matching with `exact` or `contain`</h4>
<p>By default query string conditions are matched on the exact value as defined in the shortcode. For looser ‘wildcard’ matching you can add a <code>match</code> attribute with the value <code>contain</code>:</p>
<pre><code>[if qs="product-type:cashmere-" match="contain"]
 Good choice! Cashmere is a wonderful fabric.
[/if]
</code></pre>
<p>This will match both <code>?product-type=cashmere-sweater</code> and <code>?product-type=cashmere-coat</code></p>
<h4>Matching on multiple values</h4>
<p>You can have a condition match on multiple values by using the semicolon as a seperator when defining allowed values. Example:</p>
<pre><code>[if qs="product-type:shoes;coat"]
  This text is displayed for people who bought either a nice pair of shoes or a great fashionable coat.
[/if]
</code></pre>
<h4>Nesting `if` statements</h4>
<p>You can nest statements but you have to use iteration. This has to do with the limitations of the built-in shortcode API.</p>
<pre><code>[if qs="tonight:the-night"]

  Tonight's the night.

  [if2 qs="future:beautiful"]

    We create our own destiny every day we live.

  [/if2]

  [if2 qs="future:platic"]

    I see sheets of plastic in your future.

  [/if2]

[/if]
</code></pre>
<p>You can nest up to if4 (4 levels).</p>


WordPress Conditional Content

heya,
I really liked your plugin. I think you should upgrade it to the latest version of WordPress. and keep updating. It is a nice plugin.
Cheers!



Impressed

haven't see that Kinda plugin at org. Easy to use and handy Plugin.
You should keep update this.
Thanks :)

Great Job!

Allows you to use shortcodes as if statements in your content to display text only if certain conditions are met.

Conditional Custom Fields Shortcode vs WordPress Conditional Content