vectorarrow

<h4>Features</h4>
Dynamic Content — Insert live data into any block using a simple template syntax: <code>{{ post.title }}</code>, <code>{{ user.name }}</code>, <code>{{ site.name }}</code>. No shortcodes, no PHP templates, no code.
Personalization — Greet visitors by name, show role-specific content, or display custom messages based on login status. Expressions are evaluated server-side on every page load.
Visibility Control — Show or hide any Gutenberg block based on conditions. Display content only for logged-in users, specific roles, or specific post states — all configured from the block sidebar.
Dynamic CSS Classes — Inject CSS classes into any block based on live data. Style blocks differently for administrators vs. guests, published vs. draft posts, and more.
20+ Built-in Filters — Transform values with chainable pipes: <code>upper</code>, <code>lower</code>, <code>truncate</code>, <code>date</code>, <code>default</code>, <code>match</code>, <code>replace</code>, <code>kebab</code>, and more. Chain them: <code>{{ post.title | upper | truncate 20 }}</code>.
Custom Fields — Access any post or user meta with <code>post.meta.my_field</code> or <code>user.meta.my_field</code>. Sensitive keys are blocked by default.
Full Expression Language — Arithmetic, comparison, ternary, logical operators, string interpolation, and bracket access. All evaluated server-side with zero frontend JavaScript.
In-Editor Autocomplete — Typing <code>{{</code> triggers smart autocomplete with categorized suggestions, icons, and live previews.
Extensible — Register custom data roots, custom filters, and custom autocomplete suggestions via WordPress hooks and JavaScript filters.
For complete syntax reference, filter documentation, and developer guides, visit the <a href="https://vectorarrow.com/docs/" rel="nofollow ugc">full documentation</a>.
<h4>How It Works</h4>
Add an expression to any block’s text content by typing <code>{{</code> and selecting your expression from the autocomplete menu. The plugin will automatically format it as an expression chip.
<pre><code>{{ post.title }}
{{ user.name | default "Guest" }}
{{ post.date | date "F j, Y" }}
{{ user.is_logged_in ? "Welcome back!" : "Hello, visitor!" }}
</code></pre>
Expressions are rendered as interactive chips in the editor and resolved server-side on every page render. No JavaScript runs on the frontend.
For the full syntax guide, data roots, and filter reference, see the <a href="https://vectorarrow.com/docs/" rel="nofollow ugc">documentation</a>.
<h4>Source Code</h4>
The full, uncompressed source code is publicly available on <a href="https://github.com/samuel-reinhardt/Vector-Expressions" rel="nofollow ugc">GitHub</a>.

Vector Expressions

Embed dynamic expressions in the Gutenberg block editor to personalize content and control block visibility.

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.


Vector Expressions vs Content Visibility for Divi Builder