Xpro Theme Builder For Elementor – FREE

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

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

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

$_POST['q'] not unslashed before sanitization. Use wp_unslash() or similar

The parameter "'orderby=date&hide_empty=0&number=1'" at position #2 of get_terms() has been deprecated since WordPress version 4.5.0. Instead do not pass the parameter.

Mismatched text domain. Expected 'xpro-theme-builder' but got 'xpro-elementor-addons'.

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

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

Using exclusionary parameters, like exclude, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.

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.

Detected usage of tax_query, possible slow query.

Processing form data without nonce verification.

Detected usage of a non-sanitized input variable: $_POST['xpro_theme_builder_meta_nounce']

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.

Plugin name "Xpro Theme Builder For Elementor - FREE" is different from the name declared in plugin header "Xpro Elementor Theme Builder".

Tested up to: 6.8 < 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.

Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.

Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.