Haktan Suren

With this very simple yet useful plugin, you can create your own rule for hiding content in your WP post or page.
Usage is very simple:
if you want to hide your content ONLY when foo=bar. Use the following.
<pre><code>[HandL_HIDE foo=bar]

Your rich content goes here. You can include anything: text, image and yes even videos (embed).

[/HandL_HIDE]
</code></pre>
The example content above will only be HIDDEN for the following URLS
<pre><code> http://yourdomain.com/?foo=bar 
 http://yourdomain.com/?foo=bar&anotherfoo=anotherbar etc..
</code></pre>
The example content above will NOT be hidden for the following URLS
<pre><code> http://yourdomain.com/?foo=otherbar 
 http://yourdomain.com/?foo= etc..
</code></pre>
Similarly if you want to show your content ONLY when foo=bar. Use the following.
<pre><code>[HandL_SHOW foo=bar]

Your rich content goes here. You can include anything: text, image and yes even videos (embed).

[/HandL_SHOW]
</code></pre>
The example content above will only be SHOWED for the following URLS
<pre><code> http://yourdomain.com/?foo=bar 
 http://yourdomain.com/?foo=bar&anotherfoo=anotherbar etc..
</code></pre>
The example content above will NOT be visible for the following URLS
<pre><code> http://yourdomain.com/?foo=otherbar 
 http://yourdomain.com/?foo= etc..
</code></pre>
You can also use OR statement in your logic. For example
if you want to show the content when foo=bar1 OR foo=bar2, simply use
<pre><code>[HandL_SHOW foo="bar1||bar2"]
</code></pre>
hide shortcode works similar way as well
<pre><code>[HandL_HIDE foo="bar1||bar2"]
</code></pre>
You can use the shortcode in Optimize Press as well. Usage is shown in screenshot section.

HandL Hide Content

HandL Hide Content is for people who want to hide contents based on the GET,REQUEST or POST parameters.

HandL AI Connector Access Control lets administrators allow/deny AI Client prompt execution on a per-plugin basis using the <code>wp_ai_client_prevent_prompt</code> filter introduced with the WordPress AI Client.
Default behavior is allow.
Learn mode (Audit & log tab) logs every AI Client call without blocking, so you can discover callers before enabling deny rules on the Plugin rules tab.
Emergency kill switch blocks all AI Client calls except plugins you list as exceptions.
Caller attribution is best-effort and is determined by inspecting the PHP call stack and mapping file paths to installed plugins.
<h3>Privacy / Data</h3>
This plugin does not send data to any external service.
If you enable recent-call logging in Settings → HandL AI Connector Access Control, it stores a local log in the WordPress options table containing:
<ul>
<li>Timestamp</li>
<li>Allow/deny decision</li>
<li>AI Client operation (e.g. <code>generate_text</code>, <code>is_supported_for_text_generation</code>)</li>
<li>Provider and model when set on the prompt builder (or model preferences)</li>
<li>Truncated prompt preview and selected generation config (best-effort)</li>
<li>Input and output token counts when the AI Client completes a generation (best-effort)</li>
<li>Best-effort calling plugin (plugin basename) and source file</li>
<li>Current user id and display name</li>
<li>Request URI</li>
</ul>
Logs are kept as a count-based ring buffer (default 200 entries, configurable 20–1000). There is no time-based TTL—older rows drop only when the buffer is full.
Logging is disabled by default.

HandL AI Connector Access Control

Control which plugins may execute prompts via the WordPress AI Client.

HandL Hide Content vs HandL AI Connector Access Control