0
Validation results

Pro

Pro

WordPress 6.7.1 theme
0
  • THEME TYPEWordPress theme 6.7.1
  • FILE NAMEpro.zip
  • FILE SIZE8560643 bytes
  • MD523f75c7ddbaafbe8e06b21b669dc5c92
  • SHA1292e836252332727c0ef38c8da43df85d99a987b
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSION6.2.4
  • CREATION DATE2023-06-13
  • LAST FILE UPDATE2023-06-13
  • LAST VALIDATION2023-06-13 10:17
  • OTHER VERSIONS

    4.2.3 : 0%

    3.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.
  2. Security breaches : Use of PHP sytem calls Found system in file Frame.php. 95: public function system($key) {Found >system in file Runtime.php. 19: $this->stack->frame()->system(Constants::Types)->rootSetup();20: $this->stack->frame()->system(Constants::Functions)->rootSetup();53: return $this->stack->frame()->system(Constants::Types)->apply( $input );70: $resolver = $this->stack->frame()->system(Constants::Types);71: $result = $resolver->apply( $this->exec( $settings[$key] ), $resolver->detect($default));
  3. Security breaches : Modification of PHP server settings Found ini_set in file StyleParser.php. 155: ini_set('xdebug.max_nesting_level', 500);
  4. Security breaches : Use of base64_decode() Found base64_decode in file PreviewState.php. 33: $decoded = (isset( $args['decode'] ) && $args['decode']) ? base64_decode( $input ) : $input;Found base64_decode in file AdminAjax.php. 100: $decoded = base64_decode( $data['request'] );Found base64_decode in file Endpoint.php. 104: return [json_decode( gzdecode( base64_decode( $data['request'] ) ), true ), $request];Found base64_decode in file Routes.php. 61: $result = json_decode( gzdecode( base64_decode( $params['request'], true ) ), true );
  5. Security breaches : Use of base64_encode() Found base64_encode in file setup.php.
     add_menu_page( $title, X_TITLE, 'manage_options', 'x-addons-home', 'x_addons_page_home', 'data:image/svg+xml;base64,' . base64_encode( pro_admin_menu_logo() ), 3 );
    Found base64_encode in file Admin.php.
     return 'data:image/svg+xml;base64,' . base64_encode( $this->dashboard_logo() );
    Found base64_encode in file Preview.php.
     $content = base64_encode( $gzip ? gzcompress( $json ) : $json );
    Found base64_encode in file Routes.php.
     $response['data'] = base64_encode( gzcompress( json_encode( $data ) ) );
    Found base64_encode in file App.php.
     $data['app'] = base64_encode( gzcompress( json_encode( $data['app'] ) ) );
    Found base64_encode in file helpers.php.
     return 'data:image/svg+xml;base64,' . base64_encode( '<svg xmlns='http://www.w3.org/2000/svg' width='{$width}px' 
  6. Malware : Operations on file system file_get_contents was found in the file Compiler.php 27: $tss = file_get_contents($filename);
  7. Admin menu : Themes should use add_theme_page() for adding admin pages. File setup.php : 137: add_menu_page( $title, X_TITLE, 'manage_options', 'x-addons-home', 'x_addonFile setup.php : 138: add_submenu_page( 'x-addons-home', $title, $title, 'manage_options', 'x-addFile Admin.php : 276: add_menu_page(File Admin.php : 287: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-298: add_submenu_page(308: add_submenu_page(File Admin.php : 287: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-298: add_submenu_page(308: add_submenu_page(File Admin.php : 287: add_submenu_page( 'cornerstone-home', $title, csi18n('admin.dashboard-menu-298: add_submenu_page(308: add_submenu_page(
  8. Hidden admin bar : Hidden admin Bar Themes should not hide admin bar. Detected in file : Preview.php.
  9. Deprecated functions : get_option get_option("home") was found in the file Wpml.php. Use home_url() instead.127: $state['url'] = get_option('home') . '/' . '?page_id=' . $translated . '&lang=' . $state['l659: $url = get_option('home') . '/' . apply_filters('cs_app_slug', 'cornerstone');
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 _x, with the arguments '%s Taxonomy', 'cornerstone' in file Conditionals.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Default Template' in file App.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 'Item' in file feature-list.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.Found a translation function that is missing a text-domain. Function __, with the arguments 'All Products' in file woocommerce.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Shop' in file woocommerce.php.Found a translation function that is missing a text-domain. Function _x, with the arguments '%s Taxonomy', 'cornerstone' in file woocommerce.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Default Template' in file helpers.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'This post is password protected. Enter the password to view comments.' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'One response to %s' in file comments.php.Found a translation function that is missing a text-domain. Function _n, with the arguments '%1$s response to %2$s', '%1$s responses to %2$s' in file comments.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Comments are closed.' in file comments.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 __x__, woocommerce, buddypress, bbpress, tgmpa, cornerstone, cornerstone , cornerstone`, \n, my-text-domain, Cornerstone, __x___.
  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.e85b008.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. favicon presence : Favicon managementPossible Favicon found in boilerplate.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  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 date/time template file date.phpThis theme does not contain optional file date.php.
  8. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  9. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  10. Use of includes : Use of include or requireThe theme appears to use include or require : Theme.php 88: require_once( $theme_setup );157: include_once( X_TEMPLATE_PATH . '/framework/$path.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( X_TEMPLATE_PATH . '/framework/legacy/cranium/headers/function21: require_once( X_TEMPLATE_PATH . '/framework/legacy/cranium/headers/function31: 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 49: require_once( $lgcy_path . '/cranium/headers/setup.php' );54: 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 : 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 : 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 36: 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 : i18n.php 13: $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 : setup.php 59: 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 : View.php 45: include( $this->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 : Export.php 402: require_once(ABSPATH . 'wp-admin/includes/media.php');403: require_once(ABSPATH . 'wp-admin/includes/file.php');404: require_once(ABSPATH . 'wp-admin/includes/image.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 : Config.php 32: $value = include( $config_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 : Templates.php 148: require_once( ABSPATH . 'wp-admin/includes/image.php' );149: require_once( ABSPATH . 'wp-admin/includes/file.php' );150: 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 : Admin.php 395: include( $this->plugin->path . '/includes/views/admin/home.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 : Updates.php 135: 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 : ElementLibrary.php 67: require_once( $this->plugin->path . '/includes/elements/prefab-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 : Elements.php 237: require_once( $path . '/bar.php' );238: require_once( $path . '/container.php' );239: require_once( $path . '/layout-grid.php' );240: require_once( $path . '/layout-cell.php' );259: 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 : ThemeManagement.php 45: require_once( $this->plugin->path . '/includes/extend/portfolio.php' );50: require_once( $this->plugin->path . '/includes/extend/custom-sidebars.php' 56: require_once(__DIR__ . '/../../../includes/standalone/Standalone.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 : Registry.php 17: require_once( cornerstone()->path . '/includes/elements/values.php' );24: require_once( cornerstone()->path . '/includes/elements/registry-setup.php'36: 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 : App.php 189: $elementIcons = include( $this->plugin->path . '/includes/elements/icons.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 : IconRepository.php 14: IconRepository::$icons = include( __DIR__ . '/../../elements/icons.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 : Plugin.php 59: require_once( $this->path . $files);63: require_once( $this->path . $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 : boot.php 28: require_once( $plugin_setup );31: 32: 33: 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( cornerstone()->path . '/includes/views/admin/home-box-auto-updates23: include( cornerstone()->path . '/includes/views/admin/home-box-support.php'32: include( cornerstone()->path . '/includes/views/admin/home-box-templates.ph41: <?php include( cornerstone()->path . '/includes/views/admin/home-sidebar.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-box-auto-updates.php 66: include( cornerstone()->path . '/includes/views/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( cornerstone()->path . '/includes/views/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( cornerstone()->path . '/includes/views/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 : raw-content.php 3: require_once(__DIR__ . '/../../classes/Services/IconRepository.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 : plugin.php 117: 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 : class-element-wrapper.php 150: include( $this->shortcode_template );242: return ( file_exists( $filename) ) ? include( $filename ): array();251: 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-settings-section.php 166: 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-classic-element-manager.php 59: require_once( $filename );74: require_once( $filename );198: require_once( '$path/definition.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 288: require_once(RS_PLUGIN_PATH . 'admin/includes/template.class.php');289: 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 : toolset.php 85: 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 : x-shortcodes.php 3: 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 : helpers.php 1564: 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.
Other checked themes