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.

theme funda

<p>Restrict Payment Methods For WooCommerce lets you dynamically control which payment gateways appear at checkout.</p>
<p>Create smart conditional rules and show or hide payment methods based on cart contents, customer details, shipping options, date conditions, and more.</p>
<p>Perfect for improving checkout experience, preventing invalid orders, and applying business-specific payment logic.</p>
<p>🔗 <a href="https://www.codesmade.com/restrict-payment-methods-for-woocommerce-documentation/" rel="nofollow ugc">Documentation</a> | <a href="https://www.codesmade.com/store/restrict-payment-methods-for-woocommerce/" rel="nofollow ugc">Upgrade to Pro</a> | <a href="https://www.codesmade.com/contact-us/" rel="nofollow ugc">Support</a></p>
<p>⭐ FREE FEATURES</p>
<ul>
<li>Easy installation and setup</li>
<li>Create multiple restriction rules</li>
<li>Enable or disable specific payment gateways</li>
<li>Advanced matching logic (AND/OR conditions)</li>
<li>User-friendly grouped condition builder</li>
</ul>
<h3>Available Conditions (Free Version)</h3>
<p>✔ Cart subtotal<br />
✔ Cart quantity<br />
✔ Specific products<br />
✔ User login status (logged in / guest)<br />
✔ User roles<br />
✔ Specific users<br />
✔ Shipping method<br />
✔ Billing country, state, city<br />
✔ Shipping country, state, city<br />
✔ Day of week<br />
✔ Date range</p>
<p>🚀 PRO FEATURES</p>
<p>Upgrade to the <a href="https://www.codesmade.com/store/restrict-payment-methods-for-woocommerce/" rel="nofollow ugc">Pro version</a> to unlock advanced payment restriction controls.</p>
<h3>Additional Conditions Available in Pro</h3>
<p>✔ Shipping class (shipping_class)<br />
✔ Product type (product_type)<br />
✔ Product stock status (stock_status)<br />
✔ Billing email (billing_email)<br />
✔ Shipping email (shipping_email)<br />
✔ Product categories (product_cat)<br />
✔ Product tags (product_tag)<br />
✔ Product brands (product_brand)</p>
<h3>Why Upgrade?</h3>
<ul>
<li>More granular checkout control  </li>
<li>Advanced B2B/B2C payment logic  </li>
<li>Improved fraud prevention  </li>
<li>Powerful category & brand-based restrictions  </li>
<li>Email-based gateway control  </li>
</ul>
<p>👉 <a href="https://www.codesmade.com/store/restrict-payment-methods-for-woocommerce/" rel="nofollow ugc">Get Pro Now</a></p>
<p>💡 Example Use Cases</p>
<ul>
<li>Show PayPal only if subtotal ≥ $50  </li>
<li>Hide Cash on Delivery if cart quantity exceeds 10  </li>
<li>Allow Bank Transfer only for logged-in users  </li>
<li>Show Stripe only on Mondays  </li>
<li>Restrict PayPal for specific billing countries  </li>
<li>Hide gateways during specific date ranges  </li>
<li>Apply multiple combined conditions in a single rule  </li>
</ul>
<p>⚙ How It Works</p>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to WooCommerce <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Payments Restrictions.</li>
<li>Create a rule.</li>
<li>Select payment gateway(s).</li>
<li>Add your conditions.</li>
<li>Save and test checkout.</li>
</ol>
<p>That’s it! Need help? Check out the <a href="https://www.codesmade.com/restrict-payment-methods-for-woocommerce-documentation/" rel="nofollow ugc">full documentation</a>.</p>
<p>📚 Documentation & Support</p>
<ul>
<li>📖 <a href="https://www.codesmade.com/restrict-payment-methods-for-woocommerce-documentation/" rel="nofollow ugc">Plugin Documentation</a></li>
<li>🛒 <a href="https://www.codesmade.com/store/restrict-payment-methods-for-woocommerce/" rel="nofollow ugc">Upgrade to Pro</a></li>
<li>🛠 <a href="https://www.codesmade.com/contact-us/" rel="nofollow ugc">Contact Support</a></li>
</ul>
<p>Compatibility</p>
<ul>
<li>Compatible with latest WooCommerce versions</li>
<li>Works with most WooCommerce-compatible payment gateways</li>
<li>Supports custom gateways following WooCommerce payment API</li>
</ul>


Restrict Payment Methods For WooCommerce

Restrict WooCommerce payment gateways based on flexible conditions like totals, products, user roles, shipping methods, and more.

Conditional Custom Fields Shortcode vs Restrict Payment Methods For WooCommerce