TJ Custom CSS

Sample message

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

Sample message

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Sample message

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

Sample message

A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.

Sample message

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

Sample message

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

Sample message

In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.

Sample message

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

Sample message

Library files that are already in the WordPress core are not permitted.

Sample message

Tested up to: 6.1 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.