92
Validation results

Brigsby

Free WordPress 4.9.1 theme

Brigsby

Free WordPress 4.9.1 theme
92
    Error 8 : Undefined index: slug
    In /home/www/themecheck/themecheck/controllers/controller_results.php line 772
  • THEME TYPEWordPress theme 4.9.1
  • FILE NAMEbrigsby.1.0.15.zip
  • FILE SIZE1282527 bytes
  • MD54f0716d69ae566cf266a42dcd4fbf3e0
  • SHA15675d3ead730131656e8d3621008781655a6dd2b
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • VERSION1.0.15
  • TAGSone-column, two-columns, three-columns, left-sidebar, right-sidebar, custom-background, custom-colors, custom-menu, custom-logo, featured-images, footer-widgets, full-width-template, microformats, sticky-post, theme-options, threaded-comments, translation-
  • CREATION DATE2017-01-26
  • LAST FILE UPDATE2017-03-04
  • LAST VALIDATION2017-03-04 19:00
  • OTHER VERSIONS

    1.3.7 : 92%

    1.0.16 : 92%

    1.0.13 : 92%

Error 8 : Undefined variable: cms
In /home/www/themecheck/themecheck/controllers/controller_results.php line 818
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag custom-logo in style.css header.
  2. theme tags : Too many subject tags
  3. 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 brigsby, hybrid-core.
  4. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  5. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  6. 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.
  7. Date and time implementation : Use of date_i18n()At least one hard coded date was found in the file footer-postfooter.php. Function get_option( 'date_format' ) should be used instead.
  8. Screenshot : Screenshot fileScreenshot dimensions are wrong! Detected: 300x643px (300:643). Ratio of width to height should be 4:3.Screenshot size is 300x643px. 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. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  2. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  3. Optional files : Presence of category template file category.phpThis theme does not contain optional file category.php.
  4. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  5. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  6. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  7. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  8. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  9. Optional files : Presence of search results template file search.phpThis theme does not contain optional file search.php.
  10. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  11. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  12. Optional files : Presence of 404 Not Found template file 404.phpThis theme does not contain optional file 404.php.
  13. Use of includes : Use of include or requireThe theme appears to use include or require : class-customize.php
    Line 65: require_once( HYBRIDEXTEND_INC . 'admin/trt-customize-pro/section-pro.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 : widget-social-icons.php
    Line 77: include( hybridextend_locate_widget( 'social-icons' ) ); // Loads the widge
    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 : widget-content-blocks.php
    Line 135: include( hybridextend_locate_widget( 'content-blocks' ) ); // Loads the wid
    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 : widget-cta.php
    Line 80: include( hybridextend_locate_widget( 'cta' ) ); // Loads the widget/cta or 
    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 : upsell.php
    Line 60: include_once( HYBRIDEXTEND_INC . 'admin/premium.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 : hoot-theme.php
    Line 55: require_once( HYBRIDEXTEND_INC . 'attr.php' );
    Line 58: require_once( HYBRIDEXTEND_INC . 'enqueue.php' );
    Line 61: require_once( HYBRIDEXTEND_INC . 'media.php' );
    Line 64: require_once( HYBRIDEXTEND_INC . 'fonts.php' );
    Line 67: require_once( HYBRIDEXTEND_INC . 'menus.php' );
    Line 70: require_once( HYBRIDEXTEND_INC . 'sidebars.php' );
    Line 73: require_once( HYBRIDEXTEND_INC . 'css.php' );
    Line 76: require_once( HYBRIDEXTEND_INC . 'template-helpers.php' );
    Line 79: require_once( HYBRIDEXTEND_INC . 'admin/trt-customize-pro/class-customize.p
    Line 80: require_once( HYBRIDEXTEND_INC . 'admin/customizer-options.php' );
    Line 94: require_once( HYBRIDEXTEND_INC . 'admin/upsell.php' );
    Line 109: require_once( HYBRIDEXTEND_INC . 'theme-setup.php' );
    Line 118: require_once( trailingslashit( get_template_directory() ) . 'premium/functi
    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 : admin.php
    Line 41: require_once( HYBRID_ADMIN . 'meta-box-post-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 : widgets.php
    Line 32: include_once( $filename );
    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 : style-builder.php
    Line 363: require_once( HYBRIDEXTEND_DIR . 'includes/sanitization.php' );
    Line 571: require_once( HYBRIDEXTEND_DIR . 'includes/sanitization.php' );
    Line 678: require_once( HYBRIDEXTEND_DIR . 'includes/sanitization.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 : customize.php
    Line 15: require_once ( HYBRIDEXTEND_DIR . 'customize/functions.php' );
    Line 16: require_once ( HYBRIDEXTEND_DIR . 'customize/interface.php' );
    Line 17: require_once ( HYBRIDEXTEND_DIR . 'customize/sanitization.php' );
    Line 18: require_once ( HYBRIDEXTEND_DIR . 'customize/style-builder.php' );
    Line 22: include_once( $file_path );
    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 : template.php
    Line 77: include( locate_template( $templates, false, false ) );
    Line 292: include( hybridextend_locate_widget( $name ) );
    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 : extend.php
    Line 97: require_once( HYBRIDEXTEND_DIR . 'includes/helpers.php' );
    Line 100: require_once( HYBRIDEXTEND_DIR . 'includes/scripts.php' );
    Line 103: require_once( HYBRIDEXTEND_DIR . 'includes/styles.php' );
    Line 106: require_once( HYBRIDEXTEND_DIR . 'includes/template.php' );
    Line 109: require_once( HYBRIDEXTEND_DIR . 'includes/color.php' );
    Line 112: require_once( HYBRIDEXTEND_DIR . 'includes/enum.php' );
    Line 115: require_once( HYBRIDEXTEND_DIR . 'includes/sanitization.php' );
    Line 129: require_once( HYBRIDEXTEND_DIR . 'customize/customize.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 : template.php
    Line 74: 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 : template-comments.php
    Line 104: require( $hybrid->comment_template[ $comment_type ] );
    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-i18n.php
    Line 49: require_once( $child_func );
    Line 53: require_once( $theme_func );
    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-customize.php
    Line 38: require_once( HYBRID_CUSTOMIZE . 'setting-array-map.php'  );
    Line 39: require_once( HYBRID_CUSTOMIZE . 'setting-image-data.php' );
    Line 42: require_once( HYBRID_CUSTOMIZE . 'control-checkbox-multiple.php' );
    Line 43: require_once( HYBRID_CUSTOMIZE . 'control-dropdown-terms.php'    );
    Line 44: require_once( HYBRID_CUSTOMIZE . 'control-palette.php'           );
    Line 45: require_once( HYBRID_CUSTOMIZE . 'control-radio-image.php'       );
    Line 46: require_once( HYBRID_CUSTOMIZE . 'control-select-group.php'      );
    Line 47: require_once( HYBRID_CUSTOMIZE . 'control-select-multiple.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-utility.php
    Line 215: 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 : hybrid.php
    Line 123: require_once( HYBRID_INC . 'class-media-meta.php'         );
    Line 124: require_once( HYBRID_INC . 'class-media-meta-factory.php' );
    Line 125: require_once( HYBRID_INC . 'class-media-grabber.php'      );
    Line 128: require_once( HYBRID_INC . 'functions-attr.php'      );
    Line 129: require_once( HYBRID_INC . 'functions-context.php'   );
    Line 130: require_once( HYBRID_INC . 'functions-i18n.php'      );
    Line 131: require_once( HYBRID_INC . 'functions-customize.php' );
    Line 132: require_once( HYBRID_INC . 'functions-filters.php'   );
    Line 133: require_once( HYBRID_INC . 'functions-head.php'      );
    Line 134: require_once( HYBRID_INC . 'functions-meta.php'      );
    Line 135: require_once( HYBRID_INC . 'functions-sidebars.php'  );
    Line 136: require_once( HYBRID_INC . 'functions-scripts.php'   );
    Line 137: require_once( HYBRID_INC . 'functions-styles.php'    );
    Line 138: require_once( HYBRID_INC . 'functions-utility.php'   );
    Line 141: require_once( HYBRID_INC . 'template.php'          );
    Line 142: require_once( HYBRID_INC . 'template-comments.php' );
    Line 143: require_once( HYBRID_INC . 'template-general.php'  );
    Line 144: require_once( HYBRID_INC . 'template-media.php'    );
    Line 145: require_once( HYBRID_INC . 'template-post.php'     );
    Line 232: require_once( HYBRID_ADMIN . '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.
Other checked themes