53
Validation results

SKT Solution

SKT Solution

WordPress 6.4.3 theme
53
  • THEME TYPEWordPress theme 6.4.3
  • FILE NAMEskt-solution.zip
  • FILE SIZE1257156 bytes
  • MD5dca4fa1aa91c398e8e59ce9903e9523a
  • SHA1e231ff5e754088d3f792dffde1508f8ba2cbc7f8
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSIONf1.0
  • TAGSone-column, left-sidebar, right-sidebar, custom-background, custom-colors, custom-header, custom-menu, featured-images, flexible-header, front-page-posting, full-width templateRTL, language-support, sticky-post, theme-options, threaded-comments, translatio
  • CREATION DATE2019-12-04
  • LAST FILE UPDATE2019-12-04
  • LAST VALIDATION2019-12-04 09:03
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Customizer : Sanitization of Customizer settings Found a Customizer setting that did not have a sanitization callback function in file settings-frontpage.php. Every call to the add_setting() method needs to have a sanitization callback function passed.
  2. Security breaches : Modification of PHP server settings Found ini_set in file core-functions.php. 12: ini_set('display_errors','Off');14: ini_set('error_reporting', E_ALL );
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag front-page-posting in style.css header.Found wrong tag full-width templateRTL in style.css header.Found wrong tag language-support in style.css header.Found wrong tag translation-ready. 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 complete, skt-complete, customizer-library.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. 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.
  5. CSS files : Presence of .sticky class.sticky css class is needed in theme css.
  6. CSS files : Presence of .bypostauthor class.bypostauthor css class is needed in theme css.
  7. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
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 term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  4. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  5. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  6. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  7. Use of includes : Use of include or requireThe theme appears to use include or require : enqueue.php 59: require(get_template_directory() . '/templates/custom-style.php');66: require(get_template_directory() . '/templates/custom-javascript.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 : extra.php 199: 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 : customizer.php 4: require(get_template_directory() . '/customizer/includes/control-toggle.php5: require(get_template_directory() . '/customizer/includes/control-info.php')6: require(get_template_directory() . '/customizer/includes/control-editor.php7: require(get_template_directory() . '/customizer/includes/control-multicheck8: require(get_template_directory() . '/customizer/includes/control-radioimg.p9: require(get_template_directory() . '/customizer/includes/helpers.php');196: require(get_template_directory() . '/customizer/controls/settings-basic.php197: require(get_template_directory() . '/customizer/controls/settings-header.ph198: require(get_template_directory() . '/customizer/controls/settings-frontpage199: require(get_template_directory() . '/customizer/controls/settings-postpage.200: require(get_template_directory() . '/customizer/controls/settings-footer.ph201: require(get_template_directory() . '/customizer/controls/settings-misc.php'202: require(get_template_directory() . '/customizer/controls/settings-shortcode203: require(get_template_directory() . '/customizer/controls/settings-sectionbu204: require(get_template_directory() . '/customizer/controls/settings-code.php'255: include_once(get_template_directory() . '/customizer/extra.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 8: <?php if( $singletype == 'single_layout1'){include('templates/rightsidebar_single_template.php');} ?>9: <?php if( $singletype == 'single_layout2'){include('templates/leftsidebar_single_template.php');} ?>10: <?php if( $singletype == 'single_layout3'){include('templates/fullwidth_single_template.php');} ?>11: <?php if( $singletype == 'single_layout4'){include('templates/nosidebar_single_template.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 : front-data.php 4: <?php include( get_page_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.
Other checked themes