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.

theme funda

Restrict Payment Methods For WooCommerce lets you control which payment gateways appear at checkout using powerful, flexible conditions.
With this plugin, you can dynamically show or hide WooCommerce payment methods based on cart contents, user roles, shipping methods, dates, and more — ensuring customers only see suitable and secure payment options.
<h3>💡 Key Features</h3>
<ul>
<li>One-click installation and intuitive setup </li>
<li>Configure multiple restriction rules for payment gateways </li>
<li>Simple admin interface with grouped conditions </li>
<li>
Enable/disable payment gateways based on:
<ul>
<li>Order total (subtotal, quantity)</li>
<li>Products, product categories, tags, brands, types, stock status</li>
<li>Shipping method and shipping class</li>
<li>Billing and shipping fields (name, address, etc.)</li>
<li>User status (logged in/out), user role, or specific users</li>
<li>Date and day-of-week conditions</li>
</ul>
</li>
<li>
Supports multi-line and multi-select conditions
</li>
<li>Advanced matching logic for robust scenarios </li>
<li>Compatible with the latest WooCommerce versions</li>
</ul>
<h3>Examples</h3>
Here are several examples of how you can use Restrict Payment Methods For WooCommerce to control which gateways appear during checkout:
<ol>
<li>
Restrict PayPal for orders below $50
<ul>
<li>Show PayPal only if the cart subtotal is greater than or equal to $50. </li>
<li>Condition used: Cart total (subtotal).</li>
</ul>
</li>
<li>
Hide Cash on Delivery for orders over 10 items
<ul>
<li>Disable COD if the total cart quantity exceeds 10. </li>
<li>Condition used: Cart quantity.</li>
</ul>
</li>
<li>
Restrict Cash on Delivery for specific products
<ul>
<li>Hide Cash on Delivery if “Gift Card” or “Custom Order” product is in the cart. </li>
<li>Condition used: Specific products.</li>
</ul>
</li>
<li>
Hide Stripe for certain product categories
<ul>
<li>Do not show Stripe for items in “Digital Products” category. </li>
<li>Condition used: Product category.</li>
</ul>
</li>
<li>
Show PayPal only for products tagged “express”
<ul>
<li>Display PayPal only when the cart contains products tagged as “express”. </li>
<li>Condition used: Product tags.</li>
</ul>
</li>
<li>
Enable Bank Transfer for “Brand A” products only
<ul>
<li>Only allow Bank Transfer if all items belong to Brand A. </li>
<li>Condition used: Product brand.</li>
</ul>
</li>
<li>
Restrict certain payment methods for “Variable” product types
<ul>
<li>Hide “Cash on Delivery” if the cart has variable products. </li>
<li>Condition used: Product type.</li>
</ul>
</li>
<li>
Disable PayPal for out-of-stock products
<ul>
<li>Prevent checkout with PayPal if any product in the cart is out of stock. </li>
<li>Condition used: Product stock status.</li>
</ul>
</li>
<li>
Enable payment methods based on shipping method
<ul>
<li>Show “Cash on Delivery” only if “Local Pickup” or “Flat Rate” shipping is selected. </li>
<li>Condition used: Shipping method.</li>
</ul>
</li>
<li>
Restrict PayPal for certain shipping classes
<ul>
<li>Hide PayPal if any cart item belongs to “Heavy Item” shipping class. </li>
<li>Condition used: Shipping class.</li>
</ul>
</li>
<li>
Restrict gateways based on billing country
<ul>
<li>Allow PayPal only for customers with a billing country of “United States”. </li>
<li>Condition used: Billing field (country).</li>
</ul>
</li>
<li>
Hide certain gateways for specific shipping zones or cities
<ul>
<li>Disable Bank Transfer for shipping city “New York”. </li>
<li>Condition used: Shipping field (city).</li>
</ul>
</li>
<li>
Enable Bank Transfer only for logged-in users
<ul>
<li>Hide Bank Transfer for guests; show only to logged-in customers. </li>
<li>Condition used: User login status.</li>
</ul>
</li>
<li>
Allow Stripe for “shop_manager” and “administrator” roles only
<ul>
<li>Restrict Stripe to specific user roles. </li>
<li>Condition used: User role.</li>
</ul>
</li>
<li>
Restrict payment methods for specific users
<ul>
<li>Disable “Cash on Delivery” for a particular customer account. </li>
<li>Condition used: Specific user.</li>
</ul>
</li>
<li>
Show Stripe only on Mondays and Fridays
<ul>
<li>Display Stripe gateway only on those two days. </li>
<li>Condition used: Day-of-week condition.</li>
</ul>
</li>
<li>
Restrict PayPal for specific date ranges
<ul>
<li>Hide PayPal between Dec 25–Jan 1 (e.g., during holidays). </li>
<li>Condition used: Date range condition.</li>
</ul>
</li>
<li>
Allow multiple conditions in a single rule
<ul>
<li>Example: Show PayPal only if subtotal ≥ $50 AND user is logged in AND it’s Friday. </li>
<li>Condition used: Multi-condition and advanced matching logic.</li>
</ul>
</li>
<li>
Enable multiple payment rules at once
<ul>
<li>Example: Create separate rules for different countries, product categories, and user roles simultaneously. </li>
<li>Condition used: Multiple rules support.</li>
</ul>
</li>
<li>
Restrict based on shipping class and subtotal together
<ul>
<li>Hide PayPal for “Heavy Item” class unless subtotal is above $200. </li>
<li>Condition used: Combined conditions.</li>
</ul>
</li>
</ol>
Each example demonstrates how you can tailor checkout payment options to your exact business logic and improve the customer experience.
<h3>Our More Plugins</h3>
<ul>
<li><a href="https://wordpress.org/plugins/short-description-and-attribute-show-loop-for-woocommerce/" rel="ugc">Short Description and Attributes Show Loop For WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/product-quote-cart-for-wc/" rel="ugc">Add to Quote For WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/gm-woo-product-list-widget/" rel="ugc">Product Shortcode – Widget – Block for WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/woo-show-single-variations-shop-category/" rel="ugc">Show Variations On Shop & Category WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/gm-variations-radio-buttons-for-woocommerce/" rel="ugc">Variation Dropdown to Radio For WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/gm-woocommerce-quote-popup/" rel="ugc">Product Enquiry for WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/pdf-catalog-woocommerce/" rel="ugc">PDF Catalog WooCommerce</a></li>
<li><a href="https://wordpress.org/plugins/display-product-variations-dropdown-on-shop-page-for-woocommerce/" rel="ugc">Display Product Variations Dropdown On Shop Page For WooCommerce</a></li>
</ul>

Restrict Payment Methods For WooCommerce

Restrict WooCommerce payment gateways based on flexible conditions like products, totals, user roles, and more. Smarter, dynamic checkout control.

Conditional Custom Fields Shortcode vs Restrict Payment Methods For WooCommerce