34
Validation results

SpicePress PRO

SpicePress PRO

WordPress 5.3 theme
34
  • THEME TYPEWordPress theme 5.3
  • FILE NAMEspicepress-pro-2.9.2.zip
  • FILE SIZE6903948 bytes
  • MD5b123445422d203e87900a41bc8b9c995
  • SHA19f0f66b3f01a3161bf555875d05479a60470037f
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSION2.9.2
  • AUTHOR URI
  • TAGSone-column, two-columns, right-sidebar, flexible-header, custom-colors, custom-menu, custom-logo, editor-style, featured-images, footer-widgets, sticky-post, threaded-comments, translation-ready
  • CREATION DATE2019-11-25
  • LAST FILE UPDATE2019-11-26
  • LAST VALIDATION2019-11-26 08:43
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 customizer_sections_settings.php. Every call to the add_setting() method needs to have a sanitization callback function passed.Found a Customizer setting that did not have a sanitization callback function in file customizer_general_settings.php. Every call to the add_setting() method needs to have a sanitization callback function passed.Found a Customizer setting that did not have a sanitization callback function in file customizer_theme_style.php. Every call to the add_setting() method needs to have a sanitization callback function passed.Found a Customizer setting that did not have a sanitization callback function in file customizer-template.php. Every call to the add_setting() method needs to have a sanitization callback function passed.
  2. Security breaches : Use of eval() Found eval in file functions.php. 28: eval( '?>$value<?php ' );
  3. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe width="'.$width.'" height="'.$height.'" src="'.$url.'" frameborder="0" allowfullscreen> in file content-video.php. 60: echo '<iframe width=''.$width.'' height=''.$height.'' src=''.$url.'' frameborder=Found <iframe width="'.$width.'" height="'.$height.'" src="'.$url.'" frameborder="0" allowfullscreen> in file index-slider.php. 179: echo '<div class='video-frame'><iframe width=''.$width.'' height=''.$height.'' src=''.$url.'' frameborder=
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.Found a translation function that is missing a text-domain. Function __, with the arguments 'Enter the Min. Size 200px and Max Size 6000px' in file customizer_general_settings.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d item', 'spicepress' in file header-navbar.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d item', 'spicepress' in file header-navbar.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d item', 'spicepress' in file header-navbar.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d item', 'spicepress' in file header-navbar.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%d item', 'spicepress' in file header-navbar.php.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the register_post_type() function, which is plugin-territory functionality.The 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. I18N implementation : Proper use of ___all(Possible variable $original_value found in translation function in functions.php. Translation function calls should not contain PHP variables.
  6. Screenshot : Screenshot fileScreenshot size is 880x660px. 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. 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 category template file category.phpThis theme does not contain optional file category.php.
  4. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  5. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  6. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  7. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  8. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  9. Use of includes : Use of include or requireThe theme appears to use include or require : customizer.php 6: require_once( $repeater_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 : customizer_sections_settings.php 4: require_once( $repeater_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 : script.php 62: require_once('custom_style.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