0
Validation results

Pro

Pro

WordPress 6.7 theme
0
  • THEME TYPEWordPress theme 6.7
  • FILE NAMEpro.zip
  • FILE SIZE7933404 bytes
  • MD50be541f47d15e4e0016981a40b01ccfa
  • SHA1d7b9f67adf9328552c24df38e0fa57e0956aca1f
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSION3.2.3
  • CREATION DATE2020-04-11
  • LAST FILE UPDATE2020-05-18
  • LAST VALIDATION2020-05-18 00:32
  • OTHER VERSIONS

    6.2.4 : 0%

    4.2.3 : 0%

This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Title : Title 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.
  2. Security breaches : Use of base64_decode() Found base64_decode in file class-router.php. 421: $decoded = base64_decode( $data['request'] );Found base64_decode in file class-preview-frame-loader.php. 23: $this->state = json_decode( base64_decode( $_POST['cs_preview_state'] ), true );Found base64_decode in file class-element-renderer.php. 363: return $this->unwrap_base64(base64_decode($match[1]));
  3. Security breaches : Use of base64_encode() Found base64_encode in file class-common.php. 
     return 'data:image/svg+xml;base64,' . base64_encode( '<svg xmlns='http://www.w3.org/2000/svg' width='{$width}px'
    Found base64_encode in file class-router.php. 
     $action_response_data['data'] = base64_encode( gzcompress( json_encode( $action_response_data['data'] ), 9
    Found base64_encode in file class-controller-app-boot.php. 
     $content = base64_encode( gzcompress( $content, 9 ) );
    Found base64_encode in file class-element-renderer.php. 
     $markup = base64_encode( apply_filters( 'cs_render_element_zone_output', $html ) );
     return '{%%{base64content ' . base64_encode( $content ) . '}%%}';
    Found base64_encode in file class-classic-renderer.php. 
     $markup = '{%%{base64content ' . base64_encode( $markup ) . ' }%%}';
  4. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe id= "preview-frame" data-preview-url-src="<?php echo $preview_url; ?> in file boilerplate.php. 8: <iframe id= 'preview-frame' data-preview-url-src='<?php echo $preview_url;
  5. Malware : Operations on file system file_get_contents was found in the file class-router.php 400: $data = json_decode( file_get_contents( 'php://input' ), true );
  6. Admin menu : Themes should use add_theme_page() for adding admin pages. File setup.php : 51: add_menu_page( $title, X_TITLE, 'manage_options', 'x-addons-home', 'x_addonFile setup.php : 52: add_submenu_page( 'x-addons-home', $title, $title, 'manage_options', 'x-addFile class-admin.php : 235: add_menu_page( $title, $title, 'manage_options', 'cornerstone-home', array(File class-admin.php : 236: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-242: add_submenu_page( $settings_location, $title, $status_title, 'manage_option252: add_submenu_page( $settings_location, $title, $settings_title, 'manage_optiFile class-admin.php : 236: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-242: add_submenu_page( $settings_location, $title, $status_title, 'manage_option252: add_submenu_page( $settings_location, $title, $settings_title, 'manage_optiFile class-admin.php : 236: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-242: add_submenu_page( $settings_location, $title, $status_title, 'manage_option252: add_submenu_page( $settings_location, $title, $settings_title, 'manage_optiFile class-status.php : 431: add_submenu_page( $path, $title, $title, 'manage_options', $path, array( $t
  7. Hidden admin bar : Hidden admin Bar Themes should not hide admin bar. Detected in file : class-preview-frame-loader.php.
  8. Inapropriate constants : Use of STYLESHEETPATH Constant STYLESHEETPATH was found in the file plugin-base.php. get_stylesheet_directory() should be used instead. 408: * Searches in the STYLESHEETPATH before TEMPLATEPATH so that themes which
  9. Inapropriate constants : Use of TEMPLATEPATH Constant TEMPLATEPATH was found in the file plugin-base.php. get_template_directory() should be used instead. 408: * Searches in the STYLESHEETPATH before TEMPLATEPATH so that themes which
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag 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 'Default Template' in file class-app.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Default Template' in file definition.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'first string', \n, 'second string' in file text-type.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'first string', \n, 'second string', "\n" in file text-type.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'first string', \n, 'second string', "\n", 'third string' in file text-type.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'first string', \n, 'second string', "\n", 'third string', 'cornerstone' in file text-type.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Form' in file gravity-forms.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Select which form you would like to display.' in file gravity-forms.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Show Title' in file gravity-forms.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Show Description' in file gravity-forms.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Enable AJAX' in file gravity-forms.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 woocommerce, __x__, buddypress, bbpress, tgmpa, cornerstone, cornerstone , \n, my-text-domain.
  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. Hidden admin bar : Hidden admin Bar in CSSThemes should not hide admin bar. Detected in file app.0ce70e6.css.
  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. 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.
  8. 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 category template file category.phpThis theme does not contain optional file category.php.
  4. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  5. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.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 archive template file archive.phpThis theme does not contain optional file archive.php.
  8. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  9. Use of includes : Use of include or requireThe theme appears to use include or require : pro.php 49: require_once('$cs_path/includes/boot.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 : tco.php 40: require_once( $this->path( 'class-tco-updates.php' ) );41: require_once( $this->path( 'class-tco-validator.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 : setup.php 20: require_once( $lgcy_path . '/cranium/headers/functions/navbar.php' );21: require_once( $lgcy_path . '/cranium/headers/functions/classes.php' );31: include( $outp_path . '/variables.php' );37: include( $stack_css_file );39: include( $outp_path . '/base.php' );40: include( $outp_path . '/masthead.php' );41: include( $outp_path . '/woocommerce.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 : setup.php 29: include( $outp_path . '/variables.php' );35: include( $stack_css_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 : setup.php 29: require_once( $lgcy_path . '/cranium/setup.php' );33: require_once( $lgcy_path . '/cranium/headers/setup.php' );38: require_once( $lgcy_path . '/cranium/footers/setup.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 : page-home.php 42: <?php include( 'page-home-box-validation.php' ); ?>47: <?php include( 'page-home-box-automatic-updates.php' ); ?>48: <?php include( 'page-home-box-support.php' ); ?>52: <?php include( 'page-home-box-design-cloud.php' ); ?>53: <?php include( 'page-home-box-theme-options-manager.php' ); ?>59: <?php include( 'page-home-box-extensions.php' ); ?>64: <?php include( 'page-home-box-approved-plugins.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 : setup.php 46: require_once( $plgn_path . '/cornerstone.php' );49: require_once( $plgn_path . '/acf-pro.php' );53: require_once( $plgn_path . '/bbpress.php' );57: require_once( $plgn_path . '/buddypress.php' );61: require_once( $plgn_path . '/gravity-forms.php' );65: require_once( $plgn_path . '/contact-form-7.php' );69: require_once( $plgn_path . '/convertplug.php' );73: require_once( $plgn_path . '/envira-gallery.php' );77: require_once( $plgn_path . '/essential-grid.php' );81: require_once( $plgn_path . '/layerslider.php' );85: require_once( $plgn_path . '/revolution-slider.php' );89: require_once( $plgn_path . '/soliloquy.php' );93: require_once( $plgn_path . '/visual-composer.php' );97: require_once( $plgn_path . '/woocommerce.php' );101: require_once( $plgn_path . '/wpml.php' );105: require_once( $plgn_path . '/ubermenu.php' );109: require_once( $plgn_path . '/the-grid.php' );113: require_once( $plgn_path . '/estimation-form.php');117: require_once( $plgn_path . '/modern-events-calendar.php');121: require_once( $plgn_path . '/hubspot.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-plugin-updater.php 82: include_once( ABSPATH . '/wp-admin/includes/plugin.php' );115: include_once( ABSPATH . '/wp-admin/includes/plugin.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 : setup.php 184: require_once( X_TEMPLATE_PATH . '/framework/functions/pro/bars/definitions/185: require_once( X_TEMPLATE_PATH . '/framework/functions/pro/bars/definitions/186: require_once( X_TEMPLATE_PATH . '/framework/functions/pro/bars/definitions/187: require_once( X_TEMPLATE_PATH . '/framework/functions/pro/bars/definitions/ 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 : styles.php 67: include( $outp_path . '/variables.php' );71: include( $outp_path . '/' . $x_stack . '.php' );72: include( $outp_path . '/base.php' );73: include( $outp_path . '/buttons.php' );74: include( $outp_path . '/widgets.php' );75: include( $outp_path . '/bbpress.php' );76: include( $outp_path . '/buddypress.php' );77: include( $outp_path . '/woocommerce.php' );78: include( $outp_path . '/gravity-forms.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 : view-routing.php 178: include( $_template_file );182: include( $_template_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 : helpers.php 543: $i18n[$namespace] = include( $filename ); 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 : fonts.php 149: 150: 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 : cornerstone.php 30: require_once 'includes/boot.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-dynamic-content-toolset.php 65: include_once( WPCF_EMBEDDED_ABSPATH . '/includes/fields-post.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-model-element-definition.php 11: //$records = include('precompiled/elements.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-admin.php 387: include( $this->locate_view( 'admin/home' ) );404: include( $this->plugin->locate_view( 'admin/settings' ) ); 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-status.php 19: require_once( ABSPATH . 'wp-admin/includes/plugin.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-updates.php 123: include_once( ABSPATH . '/wp-admin/includes/plugin.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-coalescence.php 7: require_once( $this->path( 'includes/classes/coalescence/class-coalescence.8: require_once( $this->path( 'includes/classes/coalescence/class-loop.php' ) 9: require_once( $this->path( 'includes/classes/coalescence/class-condition.ph10: require_once( $this->path( 'includes/classes/coalescence/class-entity.php' 11: require_once( $this->path( 'includes/classes/coalescence/class-expression.p12: require_once( $this->path( 'includes/classes/coalescence/class-formation.ph13: require_once( $this->path( 'includes/classes/coalescence/class-reducer.php'14: require_once( $this->path( 'includes/classes/coalescence/class-template.php15: require_once( $this->path( 'includes/classes/coalescence/class-template-nod16: require_once( $this->path( 'includes/classes/coalescence/class-template-dec17: require_once( $this->path( 'includes/classes/coalescence/class-template-dir 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-integration-manager.php 119: require_once( $filename ); 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-controller-templates.php 142: require_once( ABSPATH . 'wp-admin/includes/image.php' );143: require_once( ABSPATH . 'wp-admin/includes/file.php' );144: require_once( ABSPATH . 'wp-admin/includes/media.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-controller-design-cloud.php 286: require_once(RS_PLUGIN_PATH . 'admin/includes/template.class.php');287: require_once(RS_PLUGIN_PATH . 'admin/includes/import.class.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-element-manager.php 119: require_once( $filename ); 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-element-registry.php 11: require_once( $this->path( 'includes/elements/values.php' ) );17: require_once( $this->path( 'includes/elements/registry-setup.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-settings-manager.php 113: require_once( $filename );254: require_once( $filename ); 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-settings-section.php 172: return ( file_exists( $filename) ) ? include( $filename ) : array(); 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-element-orchestrator.php 124: require_once( $filename );166: require_once( $filename );220: require_once( $filename ); 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-element-wrapper.php 162: include( $this->shortcode_template );281: return ( file_exists( $filename) ) ? include( $filename ): array();290: include( $filename ); 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-layout-manager.php 67: $data = include( $filename );88: $data = include( $filename ); 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 : boot.php 12: 13: 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 : plugin-base.php 473: include( $template );500: include( $view );548: $value = include( $config_path );761: include( $template );795: include( $view ); 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 : tco.php 40: require_once( $this->path( 'class-tco-updates.php' ) );41: require_once( $this->path( 'class-tco-validator.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 : home.php 17: include( $this->locate_view( 'admin/home-box-auto-updates' ) );23: include( $this->locate_view( 'admin/home-box-support' ) );32: include( $this->locate_view( 'admin/home-box-templates' ) );41: <?php include( $this->locate_view( 'admin/home-sidebar' ) ); ?> 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-box-auto-updates.php 66: include( $this->locate_view( 'admin/home-validate-overlay' ) ); 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-box-support.php 43: include( $this->locate_view( 'admin/home-validate-overlay' ) ); 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-box-templates.php 62: include( $this->locate_view( 'admin/home-validate-overlay' ) ); 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 : shim.php 274: include( $_template_file );278: include( $_template_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 : cornerstone-plugin.php 156: require_once( $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 : x-shortcodes.php 24: include_once( ABSPATH . '/wp-admin/includes/plugin.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 : x-theme.php 70: require_once( CS()->path( 'includes/extend/portfolio.php' ) );73: require_once( CS()->path( 'includes/extend/custom-sidebars.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
57

WordPress 6.7 theme

0

WordPress 6.7 theme

14

WordPress 6.7 theme