0
Validation results

X

X

WordPress 6.7 theme
0
  • THEME TYPEWordPress theme 6.7
  • FILE NAMEx.zip
  • FILE SIZE5091750 bytes
  • MD5f554a13bc77e87bb57370b66f23dd605
  • SHA1e66c3b4444697157281285957245e25c40ad9782
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEME URIhttp://theme.co/x/
  • VERSION6.0.4
  • AUTHOR URI
  • CREATION DATE2020-10-04
  • LAST FILE UPDATE2020-10-04
  • LAST VALIDATION2020-10-04 17:17
  • OTHER VERSIONS

    7.2.3 : 54%

    4.0.7 : 0%

    3.2.3 : 0%

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 register.php. Every call to the add_setting() method needs to have a sanitization callback function passed.
  2. Title : Title No reference to add_theme_support( "title-tag" ) was found in the theme.The theme needs to have <title> tags, ideally in the header.php file.The theme needs to have a call to wp_title(), ideally in the header.php file.
  3. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe width="560" height="315" src="//www.youtube.com/embed/WxfZkMm3wcg" frameborder="0" allowfullscreen> in file data-portfolio-items.php. 203: '_x_portfolio_embed' => '<iframe width='560' height='315' src='//www.youtube.com/embed/WxfZkMm3wcg' Found <iframe src="//player.vimeo.com/video/3514904" width="500" height="281" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen> in file data-posts.php. 188: '_x_video_embed' => '<iframe src='//player.vimeo.com/video/3514904' width='500' height='281' fra
  4. Malware : Operations on file system file_put_contents was found in the file class-x-demo-import-processor.php 188: file_put_contents( $temp, file_get_contents($url) );file_get_contents was found in the file class-x-demo-import-processor.php 188: file_put_contents( $temp, file_get_contents($url) );
  5. Admin menu : Themes should use add_theme_page() for adding admin pages. File setup.php : 95: add_menu_page( 'Validation', X_TITLE, 'manage_options', 'x-addons-home', 'xFile setup.php : 96: add_submenu_page( 'x-addons-home', 'Validation', 'Validation', 'manage_opti
  6. Inapropriate constants : Use of STYLESHEETPATH Constant STYLESHEETPATH was found in the file setup.php. get_stylesheet_directory() should be used instead. 79: if ( file_exists( STYLESHEETPATH . '/' . $template ) ) {Constant STYLESHEETPATH was found in the file setup.php. get_stylesheet_directory() should be used instead. 74: if ( file_exists( STYLESHEETPATH . '/' . $template ) ) {
  7. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was cornerstone.zip.
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 'Update Plugin' in file class-x-plugin-upgrader-skin.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'There is a new version of %1$s available. <a href="%2$s" class="thickbox" title="%3$s">View version %4$s details</a>.' in file class-plugin-updater.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'There is a new version of %1$s available. <a href="%2$s" class="thickbox" title="%3$s">View version %4$s details</a>. %5$s' in file class-plugin-updater.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'There is a new version of %1$s available. <a href="%2$s" class="thickbox" title="%3$s">View version %4$s details</a> or <a href="%5$s">update now</a>.' in file class-plugin-updater.php.Found a translation function that is missing a text-domain. Function _e, with the arguments '__x__' in file setup.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__, buddypress, bbpress.
  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. Unwanted files : hidden file(s) or folder(s).ds_store was found.
  5. Line endings consistency : Both DOS and UNIX style line endingsFound a mix of \r\n and \n line endings in file preloader.php.Found a mix of \r\n and \n line endings in file transients.php.
  6. Hidden admin bar : Hidden admin Bar in CSSThemes should not hide admin bar. Detected in file integrity-light.css.
  7. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  8. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  9. 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.
  10. I18N implementation : Proper use of _e(Possible variable $text found in translation function in setup.php. Translation function calls should not contain PHP variables.
  11. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
  12. 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 meta.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  2. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file change-avatar.php.13: <p><?php _e( 'Your profile photo will be used on your profile and throughout the site. If there is a <a href='http://gravatar.com'>Gravatar</a> associated with your account email we wil69: <p><?php _e( 'Your profile photo will be used on your profile and throughout the site. To change your profile photo, please create an account with <a href='http://gravatar.com'>Gravatar</a> using the same email address as you used 13: <p><?php _e( 'Your profile photo will be used on your profile and throughout the site. If there is a <a href='http://gravatar.com'>Gravatar</a> associated with your account email we wil69: <p><?php _e( 'Your profile photo will be used on your profile and throughout the site. To change your profile photo, please create an account with <a href='http://gravatar.com'>Gravatar</a> using the same email address as you used Possible hard-coded links were found in the file page-home.php.81: <a href='https://theme.co/x/' target='_blank'><?php x_tco_product_logo( X_SLUG, 'tco81: <a href='https://theme.co/x/' target='_blank'><?php x_tco_product_logo( X_SLUG, 'tco83: <a href='https://theme.co/' target='_blank'><?php x_tco()->themeco_logo( 'tco-cta-lo88: <a class='tco-cta-action' href='https://theme.co/apex/licenses/' target='_blank'><?php _e( 'Manage LicensesPossible hard-coded links were found in the file class-addons-updates.php.246: 'message' => __( 'Could not retrieve extensions list. For assistance, please start by reviewing our article on troubleshooting <a href='https://theme.co/apex/kb/connection-issues/'>connection issues.</a>', '__x_Possible hard-coded links were found in the file ubermenu.php.37: define('UBERMENU_PACKAGED_THEME_UPDATES_NOTICE', 'Purchase not required. Your license of UberMenu is included with your X license purchase. If your X license is validated (<a href='https://theme.co/apex/kb/product-validation/'>explained here</a>), your cop42: define('UBERMENU_PACKAGED_THEME_SUPPORT_NOTICE', 'Purchase not required. Your license of UberMenu is included with your X license purchase. If your X license is validated (<a href='https://theme.co/apex/kb/product-validation/'>explained here</a>), your cop37: define('UBERMENU_PACKAGED_THEME_UPDATES_NOTICE', 'Purchase not required. Your license of UberMenu is included with your X license purchase. If your X license is validated (<a href='https://theme.co/apex/kb/product-validation/'>explained here</a>), your cop42: define('UBERMENU_PACKAGED_THEME_SUPPORT_NOTICE', 'Purchase not required. Your license of UberMenu is included with your X license purchase. If your X license is validated (<a href='https://theme.co/apex/kb/product-validation/'>explained here</a>), your copPossible hard-coded links were found in the file visual-composer.php.5139: $message = '<div class='messagebox_text'><p>' . __( 'The layout you are trying to use on this page does not conform to Visual Composer&#39;s layout guidelines. For more information on this situation and how to avoid this error going forward, please see our <a href='http://theme.co/x/member/kb/solutions-to-potential-setup-issues-visual-compPossible hard-coded links were found in the file tco-setup.php.93: 'connection-error' => __( 'Could not establish connection. For assistance, please start by reviewing our article on troubleshooting <a href='https://theme.co/apex/kb/connection-issues/'>connection issues.</a>', '__x_Possible hard-coded links were found in the file theme-overview.php.5: 'site-not-validated' => __('Your license of X is <strong class='tco-c-nope'>not validated</strong>. Place your Envato purchase code or Themeco license to unlock automatic updates, access to support, and Extensions. <a href='https://theme.co/apex/kb/product-validation/' target='_blank'>Learn more</a8: 'how-do-i-unlock' => __( 'If you have purchased X from ThemeForest already, you can find your purchase code <a href='https://theme.co/apex/images/find-item-purchase-code.png' target='_blank'>hPossible hard-coded links were found in the file class-addons-demo-content.php.78: $data['error'] = __( 'Unable to retrieve demo content. Your WordPress install may be having issues making outbound HTTP requests. For more information, please review the <a href='https://theme.co/community/kb/connection-issues/'>connection issues</a> art91: $data['error'] = __( 'No demos found. Refreshing this page may resolve the issue. If it persists, please review the <a href='https://theme.co/community/kb/connection-issues/'>connection issues</a> art78: $data['error'] = __( 'Unable to retrieve demo content. Your WordPress install may be having issues making outbound HTTP requests. For more information, please review the <a href='https://theme.co/community/kb/connection-issues/'>connection issues</a> art91: $data['error'] = __( 'No demos found. Refreshing this page may resolve the issue. If it persists, please review the <a href='https://theme.co/community/kb/connection-issues/'>connection issues</a> art
  3. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  4. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  5. Optional files : Presence of category template file category.phpThis theme does not contain optional file category.php.
  6. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  7. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  8. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  9. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  10. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  11. Optional files : Presence of search results template file search.phpThis theme does not contain optional file search.php.
  12. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  13. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  14. Use of includes : Use of include or requireThe theme appears to use include or require : x.php 60: require_once( '$modules_path/class-addons-demo-content.php' );61: require_once( '$modules_path/class-addons-cornerstone.php' );77: require( '$markup_path/page-home-box-demo-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 : 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' );37: 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 : register.php 30: include 'common.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: require_once( $csoptions_path . '/register.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 342: require_once( $meta_path . '/entries.php' );343: require_once( $meta_path . '/taxonomies.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 : ajax-handler.php 66: include_once( '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 : setup.php 55: require_once( 'helper.php' );85: require_once( 'xcs.php' );97: require_once( 'data-pages.php' );98: require_once( 'data-posts.php' );99: require_once( 'data-portfolio-items.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 83: include_once( ABSPATH . '/wp-admin/includes/plugin.php' );116: 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 : page-home.php 45: <?php require( 'markup/page-home-box-validation.php' ); ?>50: <?php require( 'markup/page-home-box-automatic-updates.php' ); ?>51: <?php require( 'markup/page-home-box-support.php' ); ?>56: <?php require( 'markup/page-home-box-theme-options-manager.php' ); ?>62: <?php require( 'markup/page-home-box-extensions.php' ); ?>67: <?php require( 'markup/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 74: require_once( $addn_path . '/updates/class-theme-updater.php' );75: require_once( $addn_path . '/updates/class-plugin-updater.php' );77: require_once( $addn_path . '/demo/legacy/ajax-handler.php' );78: require_once( $addn_path . '/demo/class-x-demo-import-session.php' );79: require_once( $addn_path . '/demo/class-x-demo-import-registry.php' );80: require_once( $addn_path . '/demo/class-x-demo-import-processor.php' );82: require_once( $addn_path . '/modules/class-addons-home.php' );83: require_once( $addn_path . '/modules/class-addons-updates.php' );84: require_once( $addn_path . '/modules/class-addons-theme-options-manager.php85: require_once( $addn_path . '/modules/class-addons-validation.php' );86: require_once( $addn_path . '/modules/class-addons-extensions.php' );88: require_once( $addn_path . '/page-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 : setup.php 27: require_once( $thmb_path . '/width.php' );28: require_once( $thmb_path . '/height.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 : data.php 208: $google_fonts = include 'google-font-data.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 : output.php 24: include( $outp_path . '/variables.php' );28: include( $outp_path . '/' . $x_stack . '.php' );29: include( $outp_path . '/base.php' );30: include( $outp_path . '/buttons.php' );31: include( $outp_path . '/widgets.php' );32: include( $outp_path . '/bbpress.php' );33: include( $outp_path . '/buddypress.php' );34: include( $outp_path . '/woocommerce.php' );35: 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 : fonts.php 26: require_once( $font_path . '/data.php' );27: require_once( $font_path . '/handling.php' );28: require_once( $font_path . '/google-fonts.php' );29: require_once( $font_path . '/control-values.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 33: require_once( $cstm_path . '/controls.php' );34: require_once( $cstm_path . '/fonts.php' );35: require_once( $cstm_path . '/register.php' );36: require_once( $cstm_path . '/output.php' );37: require_once( $cstm_path . '/transients.php' );38: require_once( $cstm_path . '/preloader.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 44: require_once( $plgn_path . '/cornerstone.php' );47: require_once( $plgn_path . '/bbpress.php' );51: require_once( $plgn_path . '/buddypress.php' );55: require_once( $plgn_path . '/convertplug.php' );59: require_once( $plgn_path . '/envira-gallery.php' );63: require_once( $plgn_path . '/essential-grid.php' );67: require_once( $plgn_path . '/layerslider.php' );71: require_once( $plgn_path . '/revolution-slider.php' );75: require_once( $plgn_path . '/soliloquy.php' );79: require_once( $plgn_path . '/visual-composer.php' );83: require_once( $plgn_path . '/woocommerce.php' );87: require_once( $plgn_path . '/wpml.php' );91: require_once( $plgn_path . '/ubermenu.php' );95: require_once( $plgn_path . '/the-grid.php' );99: require_once( $plgn_path . '/estimation-form.php');103: require_once( $plgn_path . '/modern-events-calendar.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-setup.php 21: require_once( X_TEMPLATE_PATH . '/framework/tco/tco.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 399: $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 : 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 : migration.php 297: 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.
Other checked themes