rvdforst

Beschränken Sie den Zugriff von bestimmte IP-Adressen auf Artikel, Seiten und die entsprechenden Media-Dateien.
Bei der Erstellung und Bearbeitung eines Artikels oder einer Seite, das Plugin fügt innerhalb des Veröffentlichen-Metaboxes der Feldbereich “Beschränkung von IP-Adressen” hinzu. Siehe <a href="https://wordpress.org/extend/plugins/rrze-access/screenshots/" rel="ugc">Screenshot</a>.
Die IP-Adressen die gefiltert werden sollen müssen im Textfeld “IP-Adressen” eingegeben werden. Regeln:
<ul>
<li>Eine IP-Adresse pro Zeile ist erlaubt</li>
<li>Nur IPv4-Adressen sind zulässig</li>
<li>Platzhalterzeichen “*” ist akzeptiert. Beispielsweise:
<ul>
<li>192.168.1.*</li>
<li>192.168.*.2</li>
<li>192.168.*</li>
<li>192.*</li>
<li>*</li>
</ul>
</li>
</ul>
Konfigurationsschritte für die Datei “.htaccess” finden Sie unter Einstellungen > Zugriffsbeschränkung-Einrichtung.

RRZE-Access

Zugriffsbeschränkung von IP-Adressen auf Artikel, Seiten und die entsprechenden Media-Dateien.

Jonathan Horowitz

Content Visibility for Divi Builder allows Sections and Modules to be displayed/hidden based on the outcome of a PHP boolean expression.
This plugin is for both the standalone Divi theme (or child themes thereof) and the Divi Builder plugin, version 3 or higher!
<h3>Developer Filters</h3>
<h4>Expression Validation Filters</h4>
The following filters allow developers to customize expression validation behavior. Add these filters in your theme’s functions.php or in a custom plugin.
<code>content_visibility_for_divi_builder_blocked_functions</code>
Filter the array of blocked function names. Functions in this list will cause an expression to fail validation. All comparisons are case-insensitive.
Example – allow <code>file_get_contents</code> (blocked by default):
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 return array_diff( $functions, array( 'file_get_contents' ) );
} );
</code></pre>
Example – block an additional function:
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 $functions[] = 'my_dangerous_function';
 return $functions;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_tokens</code>
Filter the array of allowed PHP token types (T_* constants). Tokens not in this list will cause an expression to fail validation. This is an advanced filter – consult the PHP tokenizer documentation before modifying.
Example – allow the T_VARIABLE token type (blocked by default, use with caution):
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_tokens', function( $tokens ) {
 $tokens[] = T_VARIABLE;
 return $tokens;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_chars</code>
Filter the array of allowed single-character tokens. Characters not in this list (such as <code>=</code>, <code>;</code>, <code>{</code>, <code>}</code>, <code>`</code>, <code>@</code>, <code>&</code>, <code>|</code>, <code>~</code>, <code>^</code>) will cause an expression to fail validation.
Example – allow the <code>&</code> character for bitwise operations:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_chars', function( $chars ) {
 $chars[] = '&';
 return $chars;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_callables</code>
Filter the array of callables (function names and <code>Class::method</code> static-method entries) the validator considers known-safe. Anything not on the allowlist (and not on the <code>blocked_functions</code> denylist) is treated as an “Unknown callable” error. Names are normalized (leading <code>\</code> stripped, <code>namespace\</code> keyword prefix stripped, lowercased) before comparison, so <code>\My\Namespace\Class::method</code>, <code>My\Namespace\Class::method</code>, and <code>namespace\My\Namespace\Class::method</code> all match the same allowlist entry. The default list ships with WordPress conditional tags (<code>is_user_logged_in</code>, <code>current_user_can</code>, <code>is_admin</code>, etc.). The Expression Validation tab’s content scanner generates a ready-to-paste snippet for this filter pre-populated with every custom callable currently in your content.
Example – allowlist a theme helper and a static service method:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_callables', function( $callables ) {
 $callables[] = 'mytheme_should_be_visible';
 $callables[] = 'MyTheme\Visibility\Service::checkUser';
 return $callables;
} );
</code></pre>

Content Visibility for Divi Builder

Thanks for maintaining this plugin. It works great. Some examples in the documentation would make the use at the beginning easier :)

Great PlugIn


I found this addon to be very useful in putting up content for a persons website. It allows you to create PHP functions or use inherent true/false functions that you can then control what content shows based on that. I find it useful in having one content being shown before a certain date and another block being set to show after a certain date. Allowing you to schedule content changes within the website.


RRZE-Access vs Content Visibility for Divi Builder