Content Visibility for Divi Builder vs Controller Fields for Contact Form 7

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! Developer Filters Expression Validation Filters The following filters allow developers to customize expression validation behavior. Add these filters in your theme’s functions.php or in a custom plugin. content_visibility_for_divi_builder_blocked_functions 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 file_get_contents (blocked by default): add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) { return array_diff( $functions, array( 'file_get_contents' ) ); } ); Example – block an additional function: add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) { $functions[] = 'my_dangerous_function'; return $functions; } ); content_visibility_for_divi_builder_allowed_tokens 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): add_filter( 'content_visibility_for_divi_builder_allowed_tokens', function( $tokens ) { $tokens[] = T_VARIABLE; return $tokens; } ); content_visibility_for_divi_builder_allowed_chars Filter the array of allowed single-character tokens. Characters not in this list (such as =, ;, {, }, `, @, &, |, ~, ^) will cause an expression to fail validation. Example – allow the & character for bitwise operations: add_filter( 'content_visibility_for_divi_builder_allowed_chars', function( $chars ) { $chars[] = '&'; return $chars; } ); content_visibility_for_divi_builder_allowed_callables Filter the array of callables (function names and Class::method static-method entries) the validator considers known-safe. Anything not on the allowlist (and not on the blocked_functions denylist) is treated as an “Unknown callable” error. Names are normalized (leading \ stripped, namespace\ keyword prefix stripped, lowercased) before comparison, so \My\Namespace\Class::method, My\Namespace\Class::method, and namespace\My\Namespace\Class::method all match the same allowlist entry. The default list ships with WordPress conditional tags (is_user_logged_in, current_user_can, is_admin, 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: add_filter( 'content_visibility_for_divi_builder_allowed_callables', function( $callables ) { $callables[] = 'mytheme_should_be_visible'; $callables[] = 'MyTheme\Visibility\Service::checkUser'; return $callables; } );

Contact Form 7 is an excellent WordPress plugin and one of the top choices of free WordPress plugins for contact forms. Controller Fields makes it even more awesome by adding dynamic content capabilities. This plugin provides new form tags for select fields, checkboxes, and radio buttons so you can use them to control the display of other fields and content. Some examples might include: Hiding or revealing additional form fields based the current value in a dropdown Hiding or revealing content when users click a checkbox Hiding or revealing information based on which radio button is currently selected Controllers and controlled fields can be nested The possibilities are endless! View Demo Preview this plugin in the WordPress Playground, a sandbox environment where you can explore the features of this plugin, both in the WordPress backend as an admin user and on the frontend. WHAT DOES IT DO? This plugin creates three (3) new form tags for controlling the appearance of other form tags (aka “controller”) and a special form tag generator button to output the HTML needed to wrap the controllable form tags inside. HOW TO USE IT After installing and activating the plugin, you will have four (4) new buttons at the top when creating or editing a Contact Form 7 form: select controller, checkbox controller, radio controller, and controlled form tag wrapper. Most of the options in their tag generators will be familiar to Contact Form 7 users but there have been some upgrades. Id Attribute The frontend script relies on unique IDs for the controller form tags, so be sure to always set one! Options There are three (3) ways you can define your options. The first method is simply typing your options with each one on a new line, e.g.: Apples Bananas Dragonfruit The second method is similar, but it allows you more control over the value and label by using | to separate them, e.g.: fruit_1 | Apples fruit_2 | Bananas fruit_3 | Dragonfruit The third method is dynamic in that you can use a shortcode to populate your options with two important provisions: The shortcode should NOT include the normal square brackets ([ and ]). So, instead of [my_shortcode key='value'] you would use my_shortcode key='value'. Any parameters in the shortcode must use single quotes. That is: my_shortcode key='value' and not my_shortcode key="value" Shortcodes used here should return a string value with the option or option group HTML. Default value This field can take static text or a shortcode. If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs: The text/shortcode must first have apostrophes converted to it’s HTML entity code, ' After that, it must be URL encoded so that spaces become %20 and other non-alphanumeric characters are converted. Placeholder Only available for the select controller form tag, this field can take static text or a shortcode. If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs: The text/shortcode must first have apostrophes converted to it’s HTML entity code, ' After that, it must be URL encoded so that spaces become %20 and other non-alphanumeric characters are converted. Read Only Attribute Simply check this box if you do not want to let users edit this field. It will add the readonly attribute to your form field. Disabled Attribute Simply check this box if you do not want to submit this field in the form. It will add the disabled attribute to your form field.