0
Validation results

Total

Total

WordPress 4.8.1 theme
0
Critical alerts
  1. Security breaches : Use of eval() Found eval in file custom-actions.php.
    Ligne198: <p><?php esc_html_e( 'If you have enabled PHP for any action you MUST wrap your code in PHP tags. The theme will use the eval() function for outputting your PHP. Please be aware of the possibly se
    Ligne278: eval( '?>$output<?php ' );
  2. Security breaches : Use of base64_decode() Found base64_decode in file vc-helpers.php.
    Ligne120: if ( $html && base64_decode( $html, true ) ) {
    Ligne121: return rawurldecode( base64_decode( strip_tags( $html ) ) );
  3. Malware : Operations on file system file_get_contents was found in the file fonts.php
    Ligne42: $faless = file_get_contents(WPEX_CSS_DIR_URI .'lib/font-awesome.min.css');
  4. Admin menu : Themes should use add_theme_page() for adding admin pages. File customizer.php :
    Ligne46: add_action( 'admin_menu', array( $this, 'add_admin_page' ), 40 );
    Ligne161: public function add_admin_page() {
    File customizer.php :
    Ligne162: add_submenu_page(
    File import-export.php :
    Ligne35: add_submenu_page(
    File custom-actions.php :
    Ligne46: add_submenu_page(
    File custom-js.php :
    Ligne38: add_submenu_page(
    File custom-login.php :
    Ligne57: add_submenu_page(
    File under-construction.php :
    Ligne40: add_submenu_page(
    File favicons.php :
    Ligne35: add_submenu_page(
    File theme-panel.php :
    Ligne30: add_action( 'admin_menu', array( $this, 'add_menu_page' ), 0 );
    Ligne238: public function add_menu_page() {
    Ligne239: add_menu_page(
    File theme-panel.php :
    Ligne30: add_action( 'admin_menu', array( $this, 'add_menu_page' ), 0 );
    Ligne238: public function add_menu_page() {
    Ligne239: add_menu_page(
    File theme-panel.php :
    Ligne256: add_submenu_page(
    File custom-css.php :
    Ligne39: add_submenu_page(
    File custom-404.php :
    Ligne35: add_submenu_page(
    File footer-builder.php :
    Ligne65: add_submenu_page(
    File class-tgm-plugin-activation.php :
    Ligne647: $this->page_hook = call_user_func( 'add_{$type}_page', $args['parent_slug'], $args['page_title'], $args['menu_t
    File image-sizes.php :
    Ligne38: add_action( 'admin_menu', array( $this, 'add_admin_page' ), 10 );
    Ligne164: public function add_admin_page() {
    File image-sizes.php :
    Ligne165: add_submenu_page(
    File portfolio-config.php :
    Ligne343: $wpex_portfolio_editor = add_submenu_page(
    File testimonials-config.php :
    Ligne263: $wpex_testimonials_editor = add_submenu_page(
    File staff-config.php :
    Ligne352: $wpex_staff_editor = add_submenu_page(
    File skins-admin.php :
    Ligne41: add_submenu_page(
  5. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was revslider.zip js_composer.zip envato-wordpress-toolkit-master.zip templatera.zip.
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in custom-js.php. Themes must not deregister core scripts.
    Ligne55: wp_deregister_script( 'ace-editor' );
    Found wp_deregister_script in custom-css.php. Themes must not deregister core scripts.
    Ligne77: wp_deregister_script( 'ace-editor' );
    Found wp_deregister_script in vc-config.php. Themes must not deregister core scripts.
    Ligne344: wp_deregister_script( 'wpb_composer_front_js' );
  2. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  3. theme tags : Presence of bad theme tagsFound wrong tag in style.css header.
  4. Text domain : Incorrect use of translation functions.Wrong installation directory for the theme name. The directory name must match the slug of the theme. This theme's correct slug and text-domain is total.
  5. Text domain : Incorrect use of translation functions.More than one text-domain is being used in this theme. This means the theme will not be compatible with WordPress.org language packs. The domains found are total, wpex, tgmpa.
  6. Plugin territory : Plugin territory functionalitiesThe theme uses the register_post_type() function, which is plugin-territory functionality.The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  7. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  8. I18N implementation : Proper use of ___all(Possible variable $val found in translation function in topbar.php. Translation function calls should not contain PHP variables. Possible variable $val found in translation function in core-functions.php. Translation function calls should not contain PHP variables.
  9. I18N implementation : Proper use of esc_html___all(Possible variable $val found in translation function in topbar.php. Translation function calls should not contain PHP variables.
  10. Screenshot : Screenshot fileScreenshot dimensions are wrong! Detected: 550x413px (550:413). Ratio of width to height should be 4:3.Screenshot size is 550x413px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.
Tip-off
  1. favicon presence : Favicon managementPossible Favicon found in favicons.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  2. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file newsletter_form.php.
    Ligne66: 'description' => esc_html__( 'Enter the MailChimp form action URL.', 'total' ) .' <a href='http://docs.shopify.com/support/configuration/store-customization/where-do-
  3. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  4. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  5. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  6. Optional files : Presence of page template file page.phpThis theme does not contain optional file page.php.
  7. Optional files : Presence of category template file category.phpThis theme does not contain optional file category.php.
  8. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  9. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  10. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  11. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  12. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  13. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  14. Use of includes : Use of include or requireThe theme appears to use include or require : overlays.php
    Ligne38: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : customizer.php
    Ligne306: require_once( $this->customizer_dir . 'customizer-controls.php' );
    Ligne307: require_once( $this->customizer_dir . 'customizer-helpers.php' );
    Ligne477: require_once( $file );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : after-update.php
    Ligne46: require_once( $dir .'redux-migrate.php' );
    Ligne73: require_once( $dir .'update-3_0_0.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : theme-panel.php
    Ligne604: require_once( $dir .'typography.php' );
    Ligne609: require_once( $dir .'under-construction.php' );
    Ligne614: require_once( $dir .'favicons.php' );
    Ligne619: require_once( $dir .'custom-404.php' );
    Ligne624: require_once( $dir .'widget-areas.php' );
    Ligne629: require_once( $dir .'custom-login.php' );
    Ligne634: require_once( $dir .'footer-builder.php' );
    Ligne639: require_once( $dir .'wp-gallery.php' );
    Ligne644: require_once( $dir .'custom-css.php' );
    Ligne649: require_once( $dir .'custom-js.php' );
    Ligne654: require_once( $dir .'custom-actions.php' );
    Ligne659: require_once( $dir .'page-animations.php' );
    Ligne663: require_once( get_template_directory() . '/skins/skins.php' );
    Ligne667: require_once( $dir .'import-export.php' );
    Ligne675: require_once( $dir .'editor-formats.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : vc-helpers.php
    Ligne18: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/parse/parse-row-atts.php
    Ligne19: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/row.php' );
    Ligne20: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/column.php' );
    Ligne21: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/single-image.php'
    Ligne29: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/autocomplete.php
    Ligne37: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/build-query.php'
    Ligne38: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/inline-js.php' )
    Ligne39: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/inline-style.php
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : vc-config.php
    Ligne27: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/vc-helpers.php' );
    Ligne79: require_once( WPEX_VCEX_DIR .'shortcodes/post_video.php' );
    Ligne80: require_once( WPEX_VCEX_DIR .'shortcodes/post_meta.php' );
    Ligne548: require_once( $val['file'] );
    Ligne551: require_once( $val );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : callout.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_callout.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : social_links.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_social_links.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : divider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_divider.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_portfolio_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : login_form.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_login_form.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_galleryslider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_galleryslider.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : teaser.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_teaser.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : heading.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_heading.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : button.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_button.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_blog_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_flexslider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_flexslider.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_staff_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : milestone.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_milestone.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : pricing.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_pricing.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_slider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_flexslider.php' ) 
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_blog_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : bullets.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_bullets.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_portfolio_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : recent_news.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_recent_news.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_testimonials_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : newsletter_form.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_newsletter_form.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : list_item.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_list_item.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : navbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_navbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : icon.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_icon.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : woocommerce_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_woocommerce_carousel.php' ) 
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_staff_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_list.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_list.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_archive.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_archive.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : spacing.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_spacing.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : terms_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_terms_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials_slider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_testimonials_slider.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : icon_box.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_icon_box.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : skillbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_skillbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : feature.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_feature_box.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_swap.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_swap.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : searchbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_searchbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'portfolio/portfolio-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'testimonials/testimonials-helpers.php' )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : woocommerce-config.php
    Ligne25: require_once( WPEX_FRAMEWORK_DIR .'woocommerce/woocommerce-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'staff/staff-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog-single-related.php
    Ligne69: <?php include( locate_template( 'partials/blog/blog-single-related-entry.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-single-related.php
    Ligne107: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-entry.php
    Ligne43: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-single-related.php
    Ligne108: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-entry.php
    Ligne43: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : skins.php
    Ligne48: require_once( WPEX_SKIN_DIR .'skins-admin.php' );
    Ligne162: require_once( $file );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.

This is a ThemeForest theme. Since Themeforest items are all checked by a human before they appear on their website, ThemeForest verification rules are more permissive than themecheck's and can give a better verification score ( Themeforest requirements ).

53
Critical alerts
  1. Security breaches : Use of eval() Found eval in file custom-actions.php.
    Ligne198: <p><?php esc_html_e( 'If you have enabled PHP for any action you MUST wrap your code in PHP tags. The theme will use the eval() function for outputting your PHP. Please be aware of the possibly se
    Ligne278: eval( '?>$output<?php ' );
  2. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was revslider.zip js_composer.zip envato-wordpress-toolkit-master.zip templatera.zip.
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in custom-js.php. Themes must not deregister core scripts.
    Ligne55: wp_deregister_script( 'ace-editor' );
    Found wp_deregister_script in custom-css.php. Themes must not deregister core scripts.
    Ligne77: wp_deregister_script( 'ace-editor' );
    Found wp_deregister_script in vc-config.php. Themes must not deregister core scripts.
    Ligne344: wp_deregister_script( 'wpb_composer_front_js' );
  2. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  3. theme tags : Presence of bad theme tagsFound wrong tag in style.css header.
  4. Text domain : Incorrect use of translation functions.Wrong installation directory for the theme name. The directory name must match the slug of the theme. This theme's correct slug and text-domain is total.
  5. Text domain : Incorrect use of translation functions.More than one text-domain is being used in this theme. This means the theme will not be compatible with WordPress.org language packs. The domains found are total, wpex, tgmpa.
  6. Plugin territory : Plugin territory functionalitiesThe theme uses the register_post_type() function, which is plugin-territory functionality.The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  7. Screenshot : Screenshot fileScreenshot dimensions are wrong! Detected: 550x413px (550:413). Ratio of width to height should be 4:3.Screenshot size is 550x413px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.
Tip-off
  1. favicon presence : Favicon managementPossible Favicon found in favicons.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  2. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file newsletter_form.php.
    Ligne66: 'description' => esc_html__( 'Enter the MailChimp form action URL.', 'total' ) .' <a href='http://docs.shopify.com/support/configuration/store-customization/where-do-
  3. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  4. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  5. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  6. Optional files : Presence of page template file page.phpThis theme does not contain optional file page.php.
  7. Optional files : Presence of category template file category.phpThis theme does not contain optional file category.php.
  8. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  9. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  10. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  11. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  12. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  13. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  14. Use of includes : Use of include or requireThe theme appears to use include or require : overlays.php
    Ligne38: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : customizer.php
    Ligne306: require_once( $this->customizer_dir . 'customizer-controls.php' );
    Ligne307: require_once( $this->customizer_dir . 'customizer-helpers.php' );
    Ligne477: require_once( $file );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : after-update.php
    Ligne46: require_once( $dir .'redux-migrate.php' );
    Ligne73: require_once( $dir .'update-3_0_0.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : theme-panel.php
    Ligne604: require_once( $dir .'typography.php' );
    Ligne609: require_once( $dir .'under-construction.php' );
    Ligne614: require_once( $dir .'favicons.php' );
    Ligne619: require_once( $dir .'custom-404.php' );
    Ligne624: require_once( $dir .'widget-areas.php' );
    Ligne629: require_once( $dir .'custom-login.php' );
    Ligne634: require_once( $dir .'footer-builder.php' );
    Ligne639: require_once( $dir .'wp-gallery.php' );
    Ligne644: require_once( $dir .'custom-css.php' );
    Ligne649: require_once( $dir .'custom-js.php' );
    Ligne654: require_once( $dir .'custom-actions.php' );
    Ligne659: require_once( $dir .'page-animations.php' );
    Ligne663: require_once( get_template_directory() . '/skins/skins.php' );
    Ligne667: require_once( $dir .'import-export.php' );
    Ligne675: require_once( $dir .'editor-formats.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : vc-helpers.php
    Ligne18: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/parse/parse-row-atts.php
    Ligne19: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/row.php' );
    Ligne20: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/column.php' );
    Ligne21: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/config/single-image.php'
    Ligne29: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/autocomplete.php
    Ligne37: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/build-query.php'
    Ligne38: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/inline-js.php' )
    Ligne39: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/helpers/inline-style.php
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : vc-config.php
    Ligne27: require_once( WPEX_FRAMEWORK_DIR .'visual-composer/vc-helpers.php' );
    Ligne79: require_once( WPEX_VCEX_DIR .'shortcodes/post_video.php' );
    Ligne80: require_once( WPEX_VCEX_DIR .'shortcodes/post_meta.php' );
    Ligne548: require_once( $val['file'] );
    Ligne551: require_once( $val );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : callout.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_callout.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : social_links.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_social_links.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : divider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_divider.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_portfolio_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : login_form.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_login_form.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_galleryslider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_galleryslider.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : teaser.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_teaser.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : heading.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_heading.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : button.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_button.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_blog_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_flexslider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_flexslider.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_staff_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : milestone.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_milestone.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : pricing.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_pricing.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_slider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_flexslider.php' ) 
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_blog_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : bullets.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_bullets.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_portfolio_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : recent_news.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_recent_news.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_testimonials_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : newsletter_form.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_newsletter_form.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : list_item.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_list_item.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : navbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_navbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : icon.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_icon.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : woocommerce_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_woocommerce_carousel.php' ) 
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_staff_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_list.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_list.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_archive.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_archive.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : spacing.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_spacing.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : terms_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_terms_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials_slider.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_testimonials_slider.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : icon_box.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_icon_box.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : post_type_carousel.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_post_type_carousel.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : skillbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_skillbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : feature.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_feature_box.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_swap.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_swap.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : image_grid.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_image_grid.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : searchbar.php
    Ligne18: include( locate_template( 'vcex_templates/vcex_searchbar.php' ) );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'portfolio/portfolio-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : testimonials-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'testimonials/testimonials-helpers.php' )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : woocommerce-config.php
    Ligne25: require_once( WPEX_FRAMEWORK_DIR .'woocommerce/woocommerce-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-config.php
    Ligne24: require_once( WPEX_FRAMEWORK_DIR .'staff/staff-helpers.php' );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : blog-single-related.php
    Ligne69: <?php include( locate_template( 'partials/blog/blog-single-related-entry.php' ) )
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-single-related.php
    Ligne107: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : portfolio-entry.php
    Ligne43: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-single-related.php
    Ligne108: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : staff-entry.php
    Ligne43: include( $template );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
    The theme appears to use include or require : skins.php
    Ligne48: require_once( WPEX_SKIN_DIR .'skins-admin.php' );
    Ligne162: require_once( $file );
    If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
Other checked themes