maurobringolf

<p>This plugin helps enforcing a set of conditions before posts can be published. You can basically integrate your pre-publish checklist into WordPress itself! The following conditions are currently supported:</p>
<ul>
<li>The post is not ‘Uncategorized’</li>
<li>The post has at least one tag</li>
</ul>
<p>If you need more conditions or have other suggestions for improvement, let me know! The best place to do so is via an issue on <a href="https://github.com/maurobringolf/publishing-conditions" rel="nofollow ugc">GitHub</a>.</p>
<h3>Usage</h3>
<p>If a post does not meet your publishing conditions and you try to publish anyway, <strong>it will be set to draft instead</strong>. You can customize your publishing conditions under <strong>Settings->Writing</strong>. That is all there is to it!</p>


Publishing Conditions

Prevent yourself from publishing unfinished posts.

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.

Publishing Conditions vs WordPress Conditional Content