97
Validation results

HitMag

Free WordPress 5.7.1 theme

HitMag

Free WordPress 5.7.1 theme
97
  • THEME TYPEWordPress theme 5.7.1
  • FILE NAMEhitmag.1.2.8.zip
  • FILE SIZE2163829 bytes
  • MD579c2c958a7dc4ba737f31dc30a66be35
  • SHA19fe6670da577db69045bd3e78b0eb2fd30ff968f
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttp://themezhut.com/themes/hitmag/
  • VERSION1.2.8
  • AUTHOR URI
  • TAGSgrid-layout,right-sidebar,two-columns,custom-logo,custom-background,custom-menu,editor-style,featured-images,footer-widgets,full-width-template,theme-options,threaded-comments,translation-ready,news,blog,e-commerce,rtl-language-support
  • CREATION DATE2021-01-13
  • LAST FILE UPDATE2021-03-02
  • LAST VALIDATION2021-03-02 15:31
This theme is open source.
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag custom-logo in style.css header.
  2. 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 hitmag, kirki.
  3. Date and time implementation : Use of date_i18n()At least one hard coded date was found in the file footer.php. Function get_option( 'date_format' ) should be used instead.
Tip-off
  1. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file customizer.php.559: 'default' => '<a href='https://themezhut.com/hitmag-wordpress-theme-documentation/' target='_blank567: 'default' => '<a href='https://themezhut.com/themes/hitmag/' target='_blank'>' . esc_html__( 'ThemPossible hard-coded links were found in the file footer.php.65: '<a href='https://themezhut.com/themes/hitmag/' target='_blank' title='HitMag WordPre
  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 category template file category.phpThis theme does not contain optional file category.php.
  6. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  7. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  8. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  9. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.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. Use of includes : Use of include or requireThe theme appears to use include or require : class-kirki-helper.php 83: require_once( ABSPATH . '/wp-admin/includes/file.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-kirki-control-fontawesome.php 42: include( $json_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 : class-upsell-customize.php 65: require_once( trailingslashit( get_template_directory() ) . '/inc/customize 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 : customizer.php 15: require( get_template_directory() . '/inc/customizer/custom-controls/contro 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