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.

Tessa (they/them), AuRise Creative

<p>Contact Form 7 is an excellent WordPress plugin and one of the top choices of free WordPress plugins for contact forms. Controller Fields makes it even more awesome by adding dynamic content capabilities. This plugin provides new form tags for select fields, checkboxes, and radio buttons so you can use them to control the display of other fields and content. Some examples might include:</p>
<ul>
<li>Hiding or revealing additional form fields based the current value in a dropdown</li>
<li>Hiding or revealing content when users click a checkbox</li>
<li>Hiding or revealing information based on which radio button is currently selected</li>
<li>Controllers and controlled fields can be nested</li>
</ul>
<p>The possibilities are endless!</p>
<h4>View Demo</h4>
<p><a href="https://wordpress.org/plugins/controller-fields-for-contact-form-7/?preview=1" rel="ugc">Preview this plugin</a> in the WordPress Playground, a sandbox environment where you can explore the features of this plugin, both in the WordPress backend as an admin user and on the frontend.</p>
<h4>WHAT DOES IT DO?</h4>
<p>This plugin creates three (3) new form tags for controlling the appearance of other form tags (aka “controller”) and a special form tag generator button to output the HTML needed to wrap the controllable form tags inside.</p>
<h4>HOW TO USE IT</h4>
<p>After installing and activating the plugin, you will have four (4) new buttons at the top when creating or editing a Contact Form 7 form: select controller, checkbox controller, radio controller, and controlled form tag wrapper. Most of the options in their tag generators will be familiar to Contact Form 7 users but there have been some upgrades.</p>
<p><strong>Id Attribute</strong></p>
<p>The frontend script relies on unique IDs for the controller form tags, so be sure to always set one!</p>
<p><strong>Options</strong></p>
<p>There are three (3) ways you can define your options. The first method is simply typing your options with each one on a new line, e.g.:</p>
<pre>Apples
Bananas
Dragonfruit</pre>
<p>The second method is similar, but it allows you more control over the value and label by using <code>|</code> to separate them, e.g.:</p>
<pre>fruit_1 | Apples
fruit_2 | Bananas
fruit_3 | Dragonfruit</pre>
<p>The third method is dynamic in that you can use a shortcode to populate your options with two important provisions:</p>
<ol>
<li>The shortcode should NOT include the normal square brackets (<code>[</code> and <code>]</code>). So, instead of <code>[my_shortcode key='value']</code> you would use <code>my_shortcode key='value'</code>.</li>
<li>Any parameters in the shortcode must use single quotes. That is: <code>my_shortcode key='value'</code> and not <code>my_shortcode key="value"</code></li>
</ol>
<p>Shortcodes used here should return a string value with the option or option group HTML.</p>
<p><strong>Default value</strong></p>
<p>This field can take static text or a shortcode. If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs:</p>
<ol>
<li>The text/shortcode must first have apostrophes converted to it’s HTML entity code, <code>'</code></li>
<li>After that, it must be URL encoded so that spaces become <code>%20</code> and other non-alphanumeric characters are converted.</li>
</ol>
<p><strong>Placeholder</strong></p>
<p>Only available for the select controller form tag, this field can take static text or a shortcode.  If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs:</p>
<ol>
<li>The text/shortcode must first have apostrophes converted to it’s HTML entity code, <code>'</code></li>
<li>After that, it must be URL encoded so that spaces become <code>%20</code> and other non-alphanumeric characters are converted.</li>
</ol>
<p><strong>Read Only Attribute</strong></p>
<p>Simply check this box if you do not want to let users edit this field. It will add the <code>readonly</code> attribute to your form field.</p>
<p><strong>Disabled Attribute</strong></p>
<p>Simply check this box if you do not want to submit this field in the form. It will add the <code>disabled</code> attribute to your form field.</p>


Controller Fields for Contact Form 7

Hide or display content in your forms created in Contact Form 7 based on user selections!

Conditional Custom Fields Shortcode vs Controller Fields for Contact Form 7