11
Validation results

BizPoint

BizPoint

WordPress 4.9.7 theme
11
    Error 8 : Undefined index: slug
    In /home/www/themecheck/themecheck/controllers/controller_results.php line 772
  • THEME TYPEWordPress theme 4.9.7
  • FILE NAMEBizPoint.zip
  • FILE SIZE598678 bytes
  • MD50814147c73b3542d8a275bb72db5d5bd
  • SHA17437108ef71d14d3abd2b2fff746fa76275361b4
  • LICENSENone
  • FILES INCLUDEDCSS, PHP, HTML, Bitmap images
  • THEME URIhttps://flexithemes.com/bizpoint-wordpress-theme/
  • VERSION1.0
  • AUTHOR URI
  • TAGSblack, green, two-columns, right-sidebar
  • CREATION DATE2016-01-28
  • LAST FILE UPDATE2017-03-05
  • LAST VALIDATION2017-03-05 21:13
  • OTHER VERSIONS

    1.1.2 : 97%

    1.1.12 : 97%

    1.0.3 : 96%

Critical alerts
  1. Title : Title The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
  2. Inapropriate constants : Use of TEMPLATEPATH Constant TEMPLATEPATH was found in the file functions.php. get_template_directory() should be used instead.
    Ligne2: require_once TEMPLATEPATH . '/lib/Themater.php';
    Constant TEMPLATEPATH was found in the file default-options.php. get_template_directory() should be used instead.
    Ligne6: 'dir' =>  TEMPLATEPATH . '/languages'
  3. Content width : Proper definition of content_width No content width has been defined. Example:
    if ( ! isset( $content_width ) ) $content_width = 900;
  4. Deprecated functions : get_bloginfo get_bloginfo('template_directory') was found in the file banners-125.php. Use get_template_directory_uri() instead.
    Ligne8: '<a href='#'><img src='' . get_bloginfo('template_directory')  . '/images/banner125.gif' alt='' title=
    Ligne9: '<a href='#'><img src='' . get_bloginfo('template_directory')  . '/images/banner125.gif' alt='' title=
Warning
  1. theme tags : Presence of bad theme tagsThe tag black has been deprecated, it must be removed from style.css header.The tag green has been deprecated, it must be removed from style.css header.
  2. 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 bizpoint.
  3. Line endings consistency : Both DOS and UNIX style line endingsFound a mix of \r\n and \n line endings in file functions.php.Found a mix of \r\n and \n line endings in file style.css.
  4. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  5. 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.
  6. CSS files : Presence of license urlLicense URI: is missing from style.css header.
  7. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  8. 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.
  9. Screenshot : Screenshot fileScreenshot size is 640x480px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.
Tip-off
  1. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file functions.php.
    Ligne41: $theme->display_widget('Banners125', array('banners' => array('<a href='https://flexithemes.com/wp-content/pro/b125-1.php' target='_blank'><img src
    Ligne46: $theme->display_widget('Text', array('text' => '<div style='text-align:center;'><a href='https://flexithemes.com/wp-content/pro/b260.php' target='_blank'><img src='
    Possible hard-coded links were found in the file menu-secondary.php.
    Ligne9: 'content', 'Please, use the <a href='nav-menus.php'><strong>menus panel</strong></a> to manage and organize menu
    Possible hard-coded links were found in the file menu-primary.php.
    Ligne9: 'content', 'Please, use the <a href='nav-menus.php'><strong>menus panel</strong></a> to manage and organize menu
    Possible hard-coded links were found in the file default-admin-options.php.
    Ligne320: $this->head_msg = '<div class='tt-notice' style='width: 800px; margin: 15px 0 0 0;'>You can buy this theme without footer links online at <a href='' . $get_theme_data['AuthorURI'] . '/buy/?theme=' . $the_theme_slug_url . '' target='_blank'>' . $get_theme_data['AuthorURI'] . '/buy/?theme=' . $the_theme_slug_url . '</a><br />Upgrading is easy. You will NOT lose your current settings or already made customizations.</div><div><a href='https://flexithemes.com/wp-content/pro/top.php' target='_blank'><img src='h
  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 term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  5. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  6. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  7. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  8. Use of includes : Use of include or requireThe theme appears to use include or require : tag.php
    Ligne41: <?php include (TEMPLATEPATH . '/sidebar.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 : archive.php
    Ligne54: <?php include (TEMPLATEPATH . '/sidebar.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 : featuredposts.php
    Ligne187: require_once(THEMATER_INCLUDES_DIR . '/featuredposts/template.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 : index.php
    Ligne39: <?php include (TEMPLATEPATH . '/sidebar.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 : page-template-contact.php
    Ligne82: <?php include (TEMPLATEPATH . '/sidebar.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 : search.php
    Ligne46: <?php include (TEMPLATEPATH . '/sidebar.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 : page.php
    Ligne32: <?php include (TEMPLATEPATH . '/sidebar.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 : page-template-sitemap.php
    Ligne83: <?php include (TEMPLATEPATH . '/sidebar.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 : category.php
    Ligne41: <?php include (TEMPLATEPATH . '/sidebar.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 : single.php
    Ligne28: <?php include (TEMPLATEPATH . '/sidebar.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 : Themater.php
    Ligne65: require_once (THEMATER_DIR . '/default-options.php');
    Ligne77: require_once (THEMATER_DIR . '/default-admin-options.php');
    Ligne288: include (THEMATER_ADMIN_DIR . '/Admin.php');
    Ligne331: include (THEMATER_DIR . '/widgets/' . $widget . '.php');
    Ligne333: include (THEMATER_DIR . '/widgets/' . $widget . '/' . $widget . '.php');
    Ligne343: include (THEMATER_INCLUDES_DIR . '/' . $include . '.php');
    Ligne345: include (THEMATER_INCLUDES_DIR . '/' . $include . '/' . $include . '.php');
    Ligne354: include (TEMPLATEPATH . '/' . $menu . '.php');
    Ligne356: include (THEMATER_DIR . '/' . $menu . '.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 : page-template-archives.php
    Ligne63: <?php include (TEMPLATEPATH . '/sidebar.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 : author.php
    Ligne41: <?php include (TEMPLATEPATH . '/sidebar.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 : 404.php
    Ligne23: <?php include (TEMPLATEPATH . '/sidebar.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