Conditional Blocks – Advanced Content Visibility Control for WordPress

Sample message

Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "CB_AFC_Integration".

Sample message

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

Sample message

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "cb_check_block_action".

Sample message

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "qm/debug".

Sample message

var_export() found. Debug code should not normally be used in production.

Sample message

load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.

Sample message

Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$class".

Sample message

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$notice['message']'.

Sample message

Resource version not set in call to wp_register_style(). This means new versions of the style may not always be loaded due to browser caching.

Sample message

Plugin name "Conditional Blocks - Advanced Content Visibility Control for WordPress" is different from the name declared in plugin header "Conditional Blocks".