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.

Davis Simiyu Wanyonyi

<p><strong>Menu Visibility Control</strong> is a lightweight, privacy-friendly WordPress plugin that lets you decide exactly <strong>who sees each menu item</strong>, directly inside the WordPress menu editor.</p>
<p>No settings pages.<br />
No lock-in.<br />
No performance overhead.</p>
<p>Everything is managed where it belongs: <strong>Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Menus</strong>.</p>
<h3>👁️ Visibility Options Per Menu Item</h3>
<p>You can control visibility based on:</p>
<ul>
<li>👥 Everyone</li>
<li>🔒 Logged-in users</li>
<li>🚪 Logged-out users</li>
<li>🧩 Specific user roles (Administrator, Editor, Subscriber, etc.)</li>
<li>📱 Device type (Desktop / Tablet / Mobile)</li>
<li>📄 Specific pages (auto-detected list)</li>
</ul>
<p>All conditions are optional and safely combined.</p>
<h3>💡 Perfect For</h3>
<ul>
<li>Membership and community websites</li>
<li>Client dashboards and intranets</li>
<li>Multi-role WordPress sites</li>
<li>Sites with mobile-specific navigation</li>
<li>Blogs that need different menus for visitors vs members</li>
</ul>
<h3>🔧 Key Features</h3>
<ul>
<li>Native integration with <strong>Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Menus</strong></li>
<li>Works with <strong>any theme or page builder</strong></li>
<li>Role-based menu visibility</li>
<li>Device-based menu visibility</li>
<li>Page-specific menu visibility</li>
<li>Auto-hidden UI (only shows options when enabled)</li>
<li>Secure (nonces, sanitization, strict validation)</li>
<li>Performance-optimized (runs only during menu rendering)</li>
<li>100% free, open-source, and donation-supported</li>
</ul>
<h3>🧠 Why Use Menu Visibility Control?</h3>
<p>Unlike large menu or membership plugins, this plugin:</p>
<ul>
<li>Uses <strong>only WordPress core hooks</strong></li>
<li>Stores <strong>minimal metadata</strong></li>
<li>Is compatible with caching, multilingual sites, and block themes</li>
<li>Does not track users or collect data</li>
</ul>
<p>It does one thing — and does it well.</p>
<h3>Support</h3>
<p>Need help or want to share feedback?</p>
<ul>
<li>Visit the <a href="https://wordpress.org/support/plugin/menu-visibility-control/" rel="ugc">support forum</a></li>
<li>Leave a <a href="https://wordpress.org/support/plugin/menu-visibility-control/reviews/#new-post" rel="ugc">review</a></li>
<li>Support development via <a href="https://knowledge.buzz/donate" rel="nofollow ugc">donation</a></li>
</ul>
<h3>License</h3>
<p>This plugin is licensed under the <strong>GPL v2 or later</strong>.</p>
<p>You are free to use, modify, and redistribute it under the same license.</p>
<p>Code is Poetry. ❤️</p>


Menu Visibility Control

Control WordPress menu item visibility based on login status, user roles, device type, or specific pages — lightweight and theme-agnostic.

Conditional Custom Fields Shortcode vs Menu Visibility Control