67
Validation results

Publisher

Publisher

WordPress 4.9.8 theme
67
Critical alerts
  1. Title : Title No reference to add_theme_support( "title-tag" ) was found in the theme.The theme needs to have <title> tags, ideally in the header.php file.The theme needs to have a call to wp_title(), ideally in the header.php file.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in custom-functions.php. Themes must not deregister core scripts.
    Ligne35: wp_deregister_script( 'jquery' );
    Found wp_deregister_script in admin_functions.php. Themes must not deregister core scripts.
    Ligne12: wp_deregister_script('jquery');
  2. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  3. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments in file custom-functions.php.Found a translation function that is missing a text-domain. Function __, with the arguments in file custom-functions.php.Found a translation function that is missing a text-domain. Function __, with the arguments '%1$s at %2$s' in file custom-functions.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Home' in file theme_functions.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 themejunkie, theme junkie, shortcodes.
  4. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  5. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  6. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  7. Deprecated functions : _preview_theme_template_filter_preview_theme_template_filter found in file theme-widgets.php. Deprecated since version 4.3.
    Ligne7: $preview_template = _preview_theme_template_filter();
  8. I18N implementation : Proper use of _e(Possible variable $themename found in translation function in theme_functions.php. Translation function calls should not contain PHP variables.
  9. I18N implementation : Proper use of ___all(Possible variable $prev found in translation function in custom-functions.php. Translation function calls should not contain PHP variables. Possible variable $next found in translation function in custom-functions.php. Translation function calls should not contain PHP variables.
  10. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  11. 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.
  12. Date and time implementation : Use of the_time()At least one hard coded date was found in the file breadcrumbs.php. Function get_option( 'date_format' ) should be used instead.
  13. 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. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file widget-flickr.php.
    Ligne46: <label for='<?php echo $this->get_field_id('id'); ?>'><?php _e('Flickr ID (<a href='http://www.idgettr.com'>idGettr</a>):','themejunkie'); ?></label>
    Possible hard-coded links were found in the file footer.php.
    Ligne36: <a href='http://templatehere.com/'>Шаблоны Wordpress</a> Thanks to <a href='http://confifihotels.com/'>Confifihotels.com</a>
  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 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 : theme-widgets.php
    Ligne20: include_once($tj_widgets_dir . $tj_widgets_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 : home.php
    Ligne3: include(TEMPLATEPATH. '/index.php');
    Ligne5: include(TEMPLATEPATH. '/archive.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 : admin_functions.php
    Ligne233: <?php include(TEMPLATEPATH . '/includes/docs/'.$value['name'].'.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 : window_post.php
    Ligne3: require_once('tj_config.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 : window_page.php
    Ligne3: require_once('tj_config.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 : tj_config.php
    Ligne9: require($wp_include);
    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.

This is a ThemeForest theme. Since Themeforest items are all checked by a human before they appear on their website, ThemeForest verification rules are more permissive than themecheck's and can give a better verification score ( Themeforest requirements ).

71
Critical alerts
  1. Title : Title No reference to add_theme_support( "title-tag" ) was found in the theme.The theme needs to have <title> tags, ideally in the header.php file.The theme needs to have a call to wp_title(), ideally in the header.php file.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
Warning
  1. core scripts deregistered : Core scripts deregistrationFound wp_deregister_script in custom-functions.php. Themes must not deregister core scripts.
    Ligne35: wp_deregister_script( 'jquery' );
    Found wp_deregister_script in admin_functions.php. Themes must not deregister core scripts.
    Ligne12: wp_deregister_script('jquery');
  2. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  3. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments in file custom-functions.php.Found a translation function that is missing a text-domain. Function __, with the arguments in file custom-functions.php.Found a translation function that is missing a text-domain. Function __, with the arguments '%1$s at %2$s' in file custom-functions.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Home' in file theme_functions.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 themejunkie, theme junkie, shortcodes.
  4. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  5. Deprecated functions : _preview_theme_template_filter_preview_theme_template_filter found in file theme-widgets.php. Deprecated since version 4.3.
    Ligne7: $preview_template = _preview_theme_template_filter();
  6. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  7. 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.
  8. Date and time implementation : Use of the_time()At least one hard coded date was found in the file breadcrumbs.php. Function get_option( 'date_format' ) should be used instead.
  9. 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. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file widget-flickr.php.
    Ligne46: <label for='<?php echo $this->get_field_id('id'); ?>'><?php _e('Flickr ID (<a href='http://www.idgettr.com'>idGettr</a>):','themejunkie'); ?></label>
    Possible hard-coded links were found in the file footer.php.
    Ligne36: <a href='http://templatehere.com/'>Шаблоны Wordpress</a> Thanks to <a href='http://confifihotels.com/'>Confifihotels.com</a>
  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 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 : theme-widgets.php
    Ligne20: include_once($tj_widgets_dir . $tj_widgets_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 : home.php
    Ligne3: include(TEMPLATEPATH. '/index.php');
    Ligne5: include(TEMPLATEPATH. '/archive.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 : admin_functions.php
    Ligne233: <?php include(TEMPLATEPATH . '/includes/docs/'.$value['name'].'.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 : window_post.php
    Ligne3: require_once('tj_config.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 : window_page.php
    Ligne3: require_once('tj_config.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 : tj_config.php
    Ligne9: require($wp_include);
    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