0
Validation results

Flatsome | Shared By Themes24x7.com

Flatsome | Shared By Themes24x7.com

WordPress 4.8.1 theme
0
Critical alerts
  1. Security breaches : Use of base64_decode() Found base64_decode in file functions.interface.php.
    Ligne229: $smof_data = unserialize(base64_decode($_POST['data'])); //100% safe - ignore theme check nag
  2. Security breaches : Use of base64_encode() Found base64_encode in file class.options_machine.php.
     $output .= '<textarea id='export_data' rows='8'>'.base64_encode(serialize($smof_data)) /* 100% safe - ignore theme check nag 
  3. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe class="block-iframe" src=""/> in file shortcodes_editor.php.
    Ligne2493: <iframe class='block-iframe' src=''/>
  4. Admin menu : Themes should use add_theme_page() for adding admin pages. File class-tgm-plugin-activation.php :
    Ligne646: $this->page_hook = call_user_func( 'add_{$type}_page', $args['parent_slug'], $args['page_title'], $args['menu_t
  5. Hidden admin bar : Hidden admin Bar Themes should not hide admin bar. Detected in file : single-blocks.php.
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in wpml.php. Themes must not deregister core scripts.
    Ligne48: wp_deregister_script('wc-cart-fragments');
  2. theme tags : Presence of bad theme tagsFound wrong tag WooCommerce in style.css header.Found wrong tag Responsive in style.css header.Found wrong tag Business in style.css header.Found wrong tag Page Builder in style.css header.
  3. 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 flatsome-shared-by-themes24x7-com.
  4. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments 'See more' in file nested-category.php.Found a translation function that is missing a text-domain. Function _n, with the arguments 'Featured Item Item', 'Featured Item Items' in file ux-featured-items.php.Found a translation function that is missing a text-domain. Function _n, with the arguments 'Featured Item Item Pending', 'Featured Item Items Pending' in file ux-featured-items.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 flatsome, woocommerce, yith-woocommerce-wishlist, flatsome-maintenance-mode, blocks, featured_itemposttype, tgmpa, text_domain, wordpress, storefront, ux-admin, wc_cpdf, theme-slug.
  5. 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.
  6. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  7. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  8. 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.
  9. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  10. CSS files : Presence of .screen-reader-text class.screen-reader-text css class is needed in your theme css. See : the Codex for an example implementation.
  11. Screenshot : Screenshot fileScreenshot size is 300x225px. 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 header.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 global.php.
    Ligne145: $smm_admin_notice = '<div id='message' class='error fade'><p>' . $smm_active_message . ' <a href='themes.php?page=optionsframework&tab=of-option-globalsettings'>' . __( 'Dea
    Possible hard-coded links were found in the file getting-started.php.
    Ligne57: <p><a href='http://docs.woothemes.com/documentation/themes/storefront/' class='button'>
    Possible hard-coded links were found in the file child-themes.php.
    Ligne25: <a href='http://www.woothemes.com/products/galleria/' class='button button-primary'>
    Ligne27: <a href='http://www.woothemes.com/products/galleria/' class='button'><?php printf( _
    Ligne25: <a href='http://www.woothemes.com/products/galleria/' class='button button-primary'>
    Ligne27: <a href='http://www.woothemes.com/products/galleria/' class='button'><?php printf( _
    Ligne39: <a href='http://www.woothemes.com/products/deli/' class='button'><?php printf( __( '
    Ligne51: <a href='http://www.woothemes.com/products/boutique/' class='button'><?php printf( _
    Possible hard-coded links were found in the file who.php.
    Ligne11: <p><a href='http://woothemes.com' class='button'><?php _e( 'Visit WooThemes', 'storefro
    Possible hard-coded links were found in the file add-ons.php.
    Ligne34: <p><a href='https://www.woothemes.com/products/storefront-designer?utm_source=product&u
    Ligne47: <p><a href='https://www.woothemes.com/products/storefront-product-hero?utm_source=produ
    Ligne99: <p><a href='https://www.woothemes.com/products/storefront-woocommerce-customiser?utm_so
    Ligne120: <?php echo sprintf( esc_html__( 'There are literally hundreds of awesome extensions available for you to use. Looking for Table Rate Shipping? Subscriptions? Product Add-ons? You can find these and more in the WooCommerce extension shop. %sGo shopping%s.', 'storefront' ), '<a href='http://www.woothemes.com/product-category/woocommerce-extensions/'>', '</a>
  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 category template file category.phpThis theme does not contain optional file category.php.
  7. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  8. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  9. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  10. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  11. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  12. Use of includes : Use of include or requireThe theme appears to use include or require : flatsome-builder.php
    Ligne67: <?php include_once('shortcodes_insert.php'); ?>
    Ligne125: include_once('shortcodes_editor.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 : welcome-screen.php
    Ligne78: require_once( ABSPATH . 'wp-load.php' );
    Ligne79: require_once( ABSPATH . 'wp-admin/admin.php' );
    Ligne80: require_once( ABSPATH . 'wp-admin/admin-header.php' );
    Ligne102: require_once( get_template_directory() . '/inc/welcome-screen/sections/intr
    Ligne110: require_once( get_template_directory() . '/inc/welcome-screen/sections/tabs
    Ligne118: require_once( get_template_directory() . '/inc/welcome-screen/sections/who.
    Ligne126: require_once( get_template_directory() . '/inc/welcome-screen/sections/gett
    Ligne134: require_once( get_template_directory() . '/inc/welcome-screen/sections/add-
    Ligne142: require_once( get_template_directory() . '/inc/welcome-screen/sections/chil
    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 : index.php
    Ligne87: require_once ( ADMIN_PATH . 'functions/functions.load.php' );
    Ligne88: require_once ( ADMIN_PATH . 'classes/class.options_machine.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.load.php
    Ligne10: require_once( ADMIN_PATH . 'functions/functions.php' );
    Ligne11: require_once( ADMIN_PATH . 'functions/functions.filters.php' );
    Ligne12: require_once( ADMIN_PATH . 'functions/functions.interface.php' );
    Ligne13: require_once( ADMIN_PATH . 'functions/functions.options.php' );
    Ligne14: require_once( ADMIN_PATH . 'functions/functions.admin.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.interface.php
    Ligne84: include_once( ADMIN_PATH . 'front-end/options.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.
Other checked themes