74
Validation results

Bryte

Bryte

WordPress 6.7 theme
74
  • THEME TYPEWordPress theme 6.7
  • FILE NAMEbryte.zip
  • FILE SIZE27181599 bytes
  • MD5916d1e9fea15e96576af169f72ecbcb9
  • SHA1ba9f4b32dc149a9c7c5e5eb8313f7359a3aed95a
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEME URIhttps://zemez.io/wordpress/
  • VERSION1.0.0
  • AUTHOR URI
  • TAGSone-column, two-columns, three-columns, left-sidebar, right-sidebar, custom-background, custom-colors, custom-menu, featured-images, post-formats, sticky-post, theme-options, threaded-comments, translation-ready, grid-layout, custom-header, custom-logo, fo
  • CREATION DATE2020-02-25
  • LAST FILE UPDATE2020-02-25
  • LAST VALIDATION2020-02-25 20:54
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was tm-woocommerce-ajax-filters.zip cherry-ld-mods-switcher.zip tm-woocommerce-quick-view.zip revslider.zip tm-style-switcher.zip cherry-testi.zip jet-elements.zip.
Warning
  1. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  2. theme tags : Presence of bad theme tagsFound wrong tag custom-logo in style.css header.
  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 bryte, woocommerce, cherry-framework.
  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. Screenshot : Screenshot fileBad 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 front page template file front-page.phpThis theme does not contain optional file front-page.php.
  3. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  4. Optional files : Presence of category template file category.phpThis theme does not contain optional file category.php.
  5. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  6. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  7. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  8. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  9. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  10. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  11. Use of includes : Use of include or requireThe theme appears to use include or require : cherry-core.php 287: require_once( $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 : cherry-customizer.php 224: require_once( $this->module_path . 'inc/class-cherry-wp-customize-iconpicke 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 : cherry5-assets-loader.php 118: require_once 'inc/cherry5-assets-loader-handle.php';119: require_once 'inc/cherry5-assets-loader-handle-css.php';120: require_once 'inc/cherry5-assets-loader-handle-js.php';128: include 'assets/min/append.min.js'; 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 : cherry-utility.php 103: require_once( $this->module_path . '/inc/cherry-' . $utilit . '-utilit.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 : class-cherry5-insertion-popup.php 131: require_once( apply_filters( 'cherry5-is__popup-template', $this->args['mod 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 : cherry5-insert-shortcode.php 167: require_once( $this->module_path . 'inc/class-cherry5-insertion-button.php168: require_once( $this->module_path . 'inc/class-cherry5-insertion-popup.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 : cherry-widget-factory.php 106: require_once( self::$module_path . '/inc/class-cherry-abstract-widget.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 : cherry-dynamic-css.php 143: require_once 'inc/class-cherry-dynamic-css-collector.php';146: include 'assets/min/cherry-css-collector.min.js';285: require_once 'inc/class-cherry-dynamic-css-utilities.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 : cherry-ui-elements.php 134: require_once( self::$module_path . 'i-ui.php' );137: require_once( self::$module_path. 'ui-element.php' );138: require_once( self::$module_path . 'inc/class-cherry-lock-element.php' );142: require_once( self::$module_path . 'inc/ui-elements/ui-' . $ui_element . '/ 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