0
Validation results

Shopme

Shopme

WordPress 4.7.5 theme
0
Critical alerts
  1. Security breaches : Use of base64_decode() Found base64_decode in file import-class.php.
    Ligne12: $options = unserialize(base64_decode($options));
    Ligne27: $widget_settings = unserialize(base64_decode($widget_settings));
    Ligne36: $sidebar_settings = unserialize(base64_decode($sidebar_settings));
    Ligne43: $meta_settings = unserialize(base64_decode($meta_settings));
    Found base64_decode in file functions-ajax.php.
    Ligne90: $options = unserialize(base64_decode(file_get_contents( $file )));
  2. Security breaches : Use of base64_encode() Found base64_encode in file twitter-api-core.php.
     $this->args['oauth_signature'] = base64_encode( hash_hmac( 'sha1', $str, $key, true ) );
    Found base64_encode in file export-class.php.
     $export = base64_encode(serialize($export));
     $widget_settings = base64_encode(serialize($this->exportWidgets()));
     $sidebar_settings = base64_encode(serialize($this->exportSidebars()));
     $meta_settings = base64_encode(serialize($this->metaData()));
  3. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe id="like_box_widget_'. self::$id_of_like_box .'" src="https://www.facebook.com/plugins/likebox.php?href='. $profile_id .'&amp;colorscheme='. $facebook_likebox_theme .'&amp;width='. $width .'&amp;height='. $height .'&amp;connections='. $connections .'&amp;stream=false&amp;show_border=false&amp;header='. $header .'&amp;" scrolling="no" frameborder="0" allowTransparency="true" style="width:'. $width .'px; height:'. $height .'px;"> in file widgets.php.
    Ligne143: echo '<iframe id='like_box_widget_'. self::$id_of_like_box .'' src='https://www.f
    Found <iframe src="https://mapsengine.google.com/map/u/0/embed?mid=z4vjH8i214vQ.kj0Xiukzzle4" width="640" height="480"> in file vc_mad_gmaps.php.
    Ligne13: 'link' => '<iframe src='https://mapsengine.google.com/map/u/0/embed?mid=z4vjH8i214vQ.k
    Found <iframe width="<?php echo $width ?>" height="<?php echo $height ?>" src="<?php echo $link ?> in file vc_mad_contact_info.php.
    Ligne82: <iframe width='<?php echo $width ?>' height='<?php echo $height ?>' src='<?
    Found <iframe src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d193578.74109040972!2d-73.97968099999999!3d40.703312749999995!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x89c24fa5d33f083b%3A0xc80b8f06e177fe62!2z0J3RjNGOLdCZ0L7RgNC6LCDQodCo0JA!5e0!3m2!1sru!2sua!4v1424385645246" width="400" height="300" style="border:0"> in file register-theme-options.php.
    Ligne2875: 'std' => '<iframe src='https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d193578.7
  4. Malware : Operations on file system fopen was found in the file functions-helper.php
    Ligne8: $handle = @fopen( $file, 'w' );
    Ligne15: $handle = fopen($file, 'r');
    Ligne50: $handle = @fopen($index_file, 'w');
    fwrite was found in the file functions-helper.php
    Ligne11: $create = fwrite( $handle, $content );
    Ligne52: fwrite( $handle, '<?php\r\necho 'Browsing the directory is not allowed!';\r
    fclose was found in the file functions-helper.php
    Ligne12: fclose( $handle );
    Ligne18: fclose( $handle );
    Ligne53: fclose( $handle );
    fopen was found in the file functions-helper.php
    Ligne8: $handle = @fopen( $file, 'w' );
    Ligne15: $handle = fopen($file, 'r');
    Ligne50: $handle = @fopen($index_file, 'w');
    fread was found in the file functions-helper.php
    Ligne16: $filecontent = fread($handle, filesize($file));
    fclose was found in the file functions-helper.php
    Ligne12: fclose( $handle );
    Ligne18: fclose( $handle );
    Ligne53: fclose( $handle );
    fopen was found in the file functions-helper.php
    Ligne8: $handle = @fopen( $file, 'w' );
    Ligne15: $handle = fopen($file, 'r');
    Ligne50: $handle = @fopen($index_file, 'w');
    fwrite was found in the file functions-helper.php
    Ligne11: $create = fwrite( $handle, $content );
    Ligne52: fwrite( $handle, '<?php\r\necho 'Browsing the directory is not allowed!';\r
    fclose was found in the file functions-helper.php
    Ligne12: fclose( $handle );
    Ligne18: fclose( $handle );
    Ligne53: fclose( $handle );
    file_get_contents was found in the file functions-ajax.php
    Ligne89: if ( function_exists( 'file_get_contents' ) && $file != '' ) {
    Ligne90: $options = unserialize(base64_decode(file_get_contents( $file )));
  5. Admin menu : Themes should use add_theme_page() for adding admin pages. File adminpages.class.php :
    Ligne35: $page = add_menu_page( $the_title, $the_title, 'manage_options', 'shopme', array(&$
  6. Deprecated functions : wp_get_http wp_get_http found in file wordpress-importer.php. Deprecated since version 4.4. Use WP_Http instead.
    Ligne866: $headers = wp_get_http( $url, $upload['file'] );
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in config.php. Themes must not deregister core scripts.
    Ligne32: wp_deregister_script('yith_wcas_frontend');
    Found wp_deregister_script in config.php. Themes must not deregister core scripts.
    Ligne407: wp_deregister_script('wc-add-to-cart-variation');
  2. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'shopme' in file twitter-api-core.php.Found a translation function that is missing a text-domain. Function __, with the arguments '%1$s is deprecated. Use %2$s instead.' in file functions-template.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'asc' in file ordering.class.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'desc' in file ordering.class.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d vote', '%d votes' in file vc_mad_blog_posts.php.Found a translation function that has an incorrect number of arguments. Function _n, with the arguments '%s download remaining', '%s downloads remaining', downloads_remaining, 'shopme' in file my-downloads.php.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'shopme' in file shipping-calculator.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'shopme' in file cart-totals.php.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 shopme, twitter-api, post_type, tgmpa, woocommerce, downloads_remaining.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Unwanted files : Windows thumbnail storethumbs.db was found.
  5. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  6. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  7. Editor style : Presence of editor styleNo reference to add_editor_style() was found in the theme. It is recommended that the theme implements editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience.
  8. I18N implementation : Proper use of _e(Possible variable $product_sort found in translation function in ordering.class.php. Translation function calls should not contain PHP variables. Possible variable $product_sort found in translation function in ordering.class.php. Translation function calls should not contain PHP variables.
  9. I18N implementation : Proper use of ___all(Possible variable $err found in translation function in twitter-api-core.php. Translation function calls should not contain PHP variables. Possible variable $text found in translation function in twitter-api-core.php. Translation function calls should not contain PHP variables. Possible variable $cvalue found in translation function in shipping-calculator.php. Translation function calls should not contain PHP variables.
  10. I18N implementation : Proper use of esc_attr_e(Possible variable $product_sort found in translation function in ordering.class.php. Translation function calls should not contain PHP variables. Possible variable $product_sort found in translation function in ordering.class.php. Translation function calls should not contain PHP variables.
  11. I18N implementation : Proper use of esc_html___all(Possible variable $text found in translation function in twitter-api-core.php. Translation function calls should not contain PHP variables. Possible variable $cvalue found in translation function in shipping-calculator.php. Translation function calls should not contain PHP variables.
  12. Screenshot : Screenshot fileScreenshot size is 880x660px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
  1. favicon presence : Favicon managementPossible Favicon found in functions-core.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  2. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  3. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  4. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  5. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  6. Use of includes : Use of include or requireThe theme appears to use include or require : theme-helper.php
    Ligne186: include(SHOPME_INCLUDES_PATH . 'widgets/templates/' . $view . '.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 : widgets.php
    Ligne268: include(SHOPME_POPWIDGET_ABSPATH . '/inc/widget.php');
    Ligne274: include(SHOPME_POPWIDGET_ABSPATH . '/inc/form.php');
    Ligne913: include(SHOPME_MAILCHIMP_ABSPATH . '/inc/widget.php');
    Ligne925: include(SHOPME_MAILCHIMP_ABSPATH . '/inc/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 : product.php
    Ligne99: require_once(ABSPATH . 'wp-admin/includes/upgrade.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 : functions-core.php
    Ligne48: include( $located );
    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 : functions-metadata.php
    Ligne3: require_once( SHOPME_INCLUDES_PATH . 'metadata/meta_values.php' );
    Ligne4: require_once( SHOPME_INCLUDES_PATH . 'metadata/functions-types.php' );
    Ligne5: require_once( SHOPME_INCLUDES_PATH . 'metadata/product.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 : config.php
    Ligne38: require($this->paths['PLUGINS'] . 'ajax_search/config.php');
    Ligne39: require($this->paths['PLUGINS'] . 'compare/config.php');
    Ligne40: require($this->paths['PLUGINS'] . 'wishlist/config.php');
    Ligne41: require($this->paths['PLUGINS'] . 'flashsale/config.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 : config.php
    Ligne46: require( self::$pathes['PLUGINS'] . 'compare/widgets/class.yith-woocompare-
    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 : config.php
    Ligne40: include( $this->paths['PHP'] . 'functions-template.php' );
    Ligne41: include( $this->paths['PHP'] . 'templates-hooks.php' );
    Ligne42: include( $this->paths['PHP'] . 'ordering.class.php' );
    Ligne43: include( $this->paths['PHP'] . 'new-badge.class.php' );
    Ligne44: include( $this->paths['PHP'] . 'common-tab.class.php' );
    Ligne46: include( $this->paths['PHP'] . 'dropdown-cart.class.php' );
    Ligne47: include( $this->paths['PHP'] . 'quick-view.class.php' );
    Ligne48: include( $this->paths['PHP'] . 'form-login.class.php' );
    Ligne49: include( $this->paths['WIDGETS_DIR'] . 'class-wc-widget-products-specials.p
    Ligne60: include( $this->paths['PHP'] . 'currency-switcher.class.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 : config.php
    Ligne54: require_once( $this->path('CONFIG_DIR', 'map.php') );
    Ligne127: 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 : map.php
    Ligne287: 
    Ligne288: 
    Ligne289: 
    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 : register-dynamic-styles.php
    Ligne57: include( SHOPME_FRAMEWORK::$path['configPath'] . 'register-color-schemes.ph
    Ligne79: require( SHOPME_BASE_PATH . 'css/schemes/dynamic-global-css-{$color_scheme}
    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 : inc-importer.php
    Ligne22: require_once($class_wp_importer);
    Ligne31: require_once($class_wp_import);
    Ligne42: include_once('import-class.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 : import-class.php
    Ligne9: if ($option_file) @include_once($option_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 : global-object.class.php
    Ligne30: include( SHOPME_FRAMEWORK::$path['configPath'] . 'register-theme-options.ph
    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 : functions-ajax.php
    Ligne70: require_once( SHOPME_FRAMEWORK::$path['frameworkPHP'] . 'config-import-expo
    Ligne85: require_once( SHOPME_FRAMEWORK::$path['frameworkPHP'] . 'config-import-expo
    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 : framework.php
    Ligne30: require_once($this->paths['frameworkPHP'] . 'functions-helper.php');
    Ligne31: require_once($this->paths['frameworkPHP'] . 'breadcrumb.class.php');
    Ligne32: require_once($this->paths['frameworkPHP'] . 'sidebar-generator.class.php');
    Ligne33: require_once($this->paths['frameworkPHP'] . 'global-object.class.php');
    Ligne34: require_once($this->paths['frameworkPHP'] . 'adminpages.class.php');
    Ligne35: require_once($this->paths['frameworkPHP'] . 'html-helper.class.php');
    Ligne36: require_once($this->paths['frameworkPHP'] . 'functions-ajax.php');
    Ligne37: require_once($this->paths['frameworkPHP'] . 'config-import-export/export-cl
    Ligne38: require_once($this->paths['frameworkPHP'] . 'dynamic-style-creator.class.ph
    Ligne39: require_once($this->paths['frameworkPHP'] . 'facebook-page-likebox.php');
    Ligne40: require_once($this->paths['frameworkPHP'] . 'class-pinterest-widgets.php');
    Ligne41: require_once($this->paths['frameworkPHP'] . 'admin-aside-panel.php');
    Ligne42: require_once($this->paths['frameworkPHP'] . 'wp-sitemap-page.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 : register-theme-options.php
    Ligne4: include('register-google-webfonts.php');
    Ligne7: include('register-color-schemes.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 : plugins.php
    Ligne8: require_once ( SHOPME_INC_PLUGINS_PATH . trailingslashit($inc) . 'init' . '
    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 ).

75
Critical alerts
  1. Deprecated functions : wp_get_http wp_get_http found in file wordpress-importer.php. Deprecated since version 4.4. Use WP_Http instead.
    Ligne866: $headers = wp_get_http( $url, $upload['file'] );
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in config.php. Themes must not deregister core scripts.
    Ligne32: wp_deregister_script('yith_wcas_frontend');
    Found wp_deregister_script in config.php. Themes must not deregister core scripts.
    Ligne407: wp_deregister_script('wc-add-to-cart-variation');
  2. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'shopme' in file twitter-api-core.php.Found a translation function that is missing a text-domain. Function __, with the arguments '%1$s is deprecated. Use %2$s instead.' in file functions-template.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'asc' in file ordering.class.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'desc' in file ordering.class.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d vote', '%d votes' in file vc_mad_blog_posts.php.Found a translation function that has an incorrect number of arguments. Function _n, with the arguments '%s download remaining', '%s downloads remaining', downloads_remaining, 'shopme' in file my-downloads.php.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'shopme' in file shipping-calculator.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'shopme' in file cart-totals.php.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 shopme, twitter-api, post_type, tgmpa, woocommerce, downloads_remaining.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Unwanted files : Windows thumbnail storethumbs.db was found.
  5. Screenshot : Screenshot fileScreenshot size is 880x660px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
  1. favicon presence : Favicon managementPossible Favicon found in functions-core.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  2. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  3. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  4. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  5. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  6. Use of includes : Use of include or requireThe theme appears to use include or require : theme-helper.php
    Ligne186: include(SHOPME_INCLUDES_PATH . 'widgets/templates/' . $view . '.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 : widgets.php
    Ligne268: include(SHOPME_POPWIDGET_ABSPATH . '/inc/widget.php');
    Ligne274: include(SHOPME_POPWIDGET_ABSPATH . '/inc/form.php');
    Ligne913: include(SHOPME_MAILCHIMP_ABSPATH . '/inc/widget.php');
    Ligne925: include(SHOPME_MAILCHIMP_ABSPATH . '/inc/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 : product.php
    Ligne99: require_once(ABSPATH . 'wp-admin/includes/upgrade.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 : functions-core.php
    Ligne48: include( $located );
    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 : functions-metadata.php
    Ligne3: require_once( SHOPME_INCLUDES_PATH . 'metadata/meta_values.php' );
    Ligne4: require_once( SHOPME_INCLUDES_PATH . 'metadata/functions-types.php' );
    Ligne5: require_once( SHOPME_INCLUDES_PATH . 'metadata/product.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 : config.php
    Ligne38: require($this->paths['PLUGINS'] . 'ajax_search/config.php');
    Ligne39: require($this->paths['PLUGINS'] . 'compare/config.php');
    Ligne40: require($this->paths['PLUGINS'] . 'wishlist/config.php');
    Ligne41: require($this->paths['PLUGINS'] . 'flashsale/config.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 : config.php
    Ligne46: require( self::$pathes['PLUGINS'] . 'compare/widgets/class.yith-woocompare-
    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 : config.php
    Ligne40: include( $this->paths['PHP'] . 'functions-template.php' );
    Ligne41: include( $this->paths['PHP'] . 'templates-hooks.php' );
    Ligne42: include( $this->paths['PHP'] . 'ordering.class.php' );
    Ligne43: include( $this->paths['PHP'] . 'new-badge.class.php' );
    Ligne44: include( $this->paths['PHP'] . 'common-tab.class.php' );
    Ligne46: include( $this->paths['PHP'] . 'dropdown-cart.class.php' );
    Ligne47: include( $this->paths['PHP'] . 'quick-view.class.php' );
    Ligne48: include( $this->paths['PHP'] . 'form-login.class.php' );
    Ligne49: include( $this->paths['WIDGETS_DIR'] . 'class-wc-widget-products-specials.p
    Ligne60: include( $this->paths['PHP'] . 'currency-switcher.class.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 : config.php
    Ligne54: require_once( $this->path('CONFIG_DIR', 'map.php') );
    Ligne127: 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 : map.php
    Ligne287: 
    Ligne288: 
    Ligne289: 
    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 : register-dynamic-styles.php
    Ligne57: include( SHOPME_FRAMEWORK::$path['configPath'] . 'register-color-schemes.ph
    Ligne79: require( SHOPME_BASE_PATH . 'css/schemes/dynamic-global-css-{$color_scheme}
    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 : inc-importer.php
    Ligne22: require_once($class_wp_importer);
    Ligne31: require_once($class_wp_import);
    Ligne42: include_once('import-class.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 : import-class.php
    Ligne9: if ($option_file) @include_once($option_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 : global-object.class.php
    Ligne30: include( SHOPME_FRAMEWORK::$path['configPath'] . 'register-theme-options.ph
    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 : functions-ajax.php
    Ligne70: require_once( SHOPME_FRAMEWORK::$path['frameworkPHP'] . 'config-import-expo
    Ligne85: require_once( SHOPME_FRAMEWORK::$path['frameworkPHP'] . 'config-import-expo
    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 : framework.php
    Ligne30: require_once($this->paths['frameworkPHP'] . 'functions-helper.php');
    Ligne31: require_once($this->paths['frameworkPHP'] . 'breadcrumb.class.php');
    Ligne32: require_once($this->paths['frameworkPHP'] . 'sidebar-generator.class.php');
    Ligne33: require_once($this->paths['frameworkPHP'] . 'global-object.class.php');
    Ligne34: require_once($this->paths['frameworkPHP'] . 'adminpages.class.php');
    Ligne35: require_once($this->paths['frameworkPHP'] . 'html-helper.class.php');
    Ligne36: require_once($this->paths['frameworkPHP'] . 'functions-ajax.php');
    Ligne37: require_once($this->paths['frameworkPHP'] . 'config-import-export/export-cl
    Ligne38: require_once($this->paths['frameworkPHP'] . 'dynamic-style-creator.class.ph
    Ligne39: require_once($this->paths['frameworkPHP'] . 'facebook-page-likebox.php');
    Ligne40: require_once($this->paths['frameworkPHP'] . 'class-pinterest-widgets.php');
    Ligne41: require_once($this->paths['frameworkPHP'] . 'admin-aside-panel.php');
    Ligne42: require_once($this->paths['frameworkPHP'] . 'wp-sitemap-page.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 : register-theme-options.php
    Ligne4: include('register-google-webfonts.php');
    Ligne7: include('register-color-schemes.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 : plugins.php
    Ligne8: require_once ( SHOPME_INC_PLUGINS_PATH . trailingslashit($inc) . 'init' . '
    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