73
Validation results

LandKit

LandKit

WordPress 6.7 theme
73
  • THEME TYPEWordPress theme 6.7
  • FILE NAMELandkit_To_Install.zip
  • FILE SIZE9154702 bytes
  • MD56d79e2f03975b20470a6834de308deb9
  • SHA1da3851793232fdda6bcb02791385b6ee4b658e7c
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEME URIhttp://socanny.com/landkit/
  • VERSION1.9
  • AUTHOR URI
  • CREATION DATE2019-12-06
  • LAST FILE UPDATE2019-12-06
  • LAST VALIDATION2019-12-06 13:15
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 hybrid-composer.zip ._hybrid-composer.zip.
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag 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 landkit, example.
  3. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  4. Custom elements : Presence of custom backgroundNo reference to custom background 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. Featured image : Use of add_theme_support( 'post-thumbnails' ) in functions.php fileNo reference to post-thumbnails was found in the theme.
  7. 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 page template file page.phpThis theme does not contain optional file page.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 : template-background-slider.php 10: include(HC_PLUGIN_PATH . '/global-content.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 : woocommerce.php 11: include(HC_PLUGIN_PATH . '/global-content.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-twosides.php 11: include(HC_PLUGIN_PATH .'/global-content.php');14: if (defined('HC_PLUGIN_PATH')) include(HC_PLUGIN_PATH . '/twosides.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 : header.php 20: include_once(HC_PLUGIN_PATH . '/inc/front-functions.php');21: include_once(HC_PLUGIN_PATH .'/global-content.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-background-video.php 10: include(HC_PLUGIN_PATH . '/global-content.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-background-image.php 10: include(HC_PLUGIN_PATH . '/global-content.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-fullpage.php 11: include(HC_PLUGIN_PATH . '/global-content.php');15: if (defined('HC_PLUGIN_PATH')) include(HC_PLUGIN_PATH . '/fullpage.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 9: include(HC_PLUGIN_PATH . '/global-content.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