11
Validation results

Gradiant Pro

Gradiant Pro

WordPress 6.5.3 theme
11
  • THEME TYPEWordPress theme 6.5.3
  • FILE NAMEgradiant-pro.zip
  • FILE SIZE10641393 bytes
  • MD5e95727788411c9189627cbeb6f4835ee
  • SHA1c0bfbd7667af69af1da8a580734cf9485ca99bb0
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSION1.9
  • TAGSone-column, two-columns, left-sidebar, right-sidebar, flexible-header, custom-background, custom-colors, custom-header, custom-menu, featured-image-header, featured-images, footer-widgets, full-width-template, theme-options, threaded-comments, translation-
  • CREATION DATE2023-04-08
  • LAST FILE UPDATE2023-04-08
  • LAST VALIDATION2023-04-08 06:52
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 gradiant-page-templates.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 gradiant-header.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 gradiant-blog.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 gradiant-contact-page.php. Every call to the add_setting() method needs to have a sanitization callback function passed.
  2. Title : Title The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
  3. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe src="<?php echo esc_url($pg_ct_map_link); ?> in file section-contact-map-info.php. 48: <div class='map'><iframe src='<?php echo esc_url($pg_ct_map_link); ?>' width='100%' height='
  4. Admin menu : Themes should use add_theme_page() for adding admin pages. File class-tgm-plugin-activation.php : 731: $this->page_hook = call_user_func( 'add_submenu_page', $args['parent_slug'], $args['page_title'], $args['menu_t
Warning
  1. 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 gradiant-pro, tgmpa, info-box.
  2. 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.
  3. I18N implementation : Proper use of _e(Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables. Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables.
  4. 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.
  5. I18N implementation : Proper use of esc_attr_e(Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables. Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables.
  6. CSS files : Presence of Theme URICould not find Theme URL.
  7. CSS files : Presence of Author URICould not find Author URI.
  8. Date and time implementation : Use of date_i18n()At least one hard coded date was found in the file extras.php. Function get_option( 'date_format' ) should be used instead.
  9. Screenshot : Screenshot fileScreenshot size is 300x225px. 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 home template file home.phpThis theme does not contain optional file home.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 author template file author.phpThis theme does not contain optional file author.php.
  8. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  9. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  10. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  11. Use of includes : Use of include or requireThe theme appears to use include or require : extras.php 659: include($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 : cpt-main.php 2: require( get_template_directory() . '/inc/cpt/gradiant-cpt-project.php');3: require( get_template_directory() . '/inc/cpt/gradiant-cpt-pricing.php');4: require( get_template_directory() . '/inc/cpt/gradiant-cpt-faq.php');5: require( get_template_directory() . '/inc/cpt/add_shortcode_faq.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 : gradiant-header.php 1109: require_once( $page_editor_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 : gradiant-custom.php 100: require_once( $page_editor_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 : theme-updater.php 10: include( dirname( __FILE__ ) . '/theme-updater-admin.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 : theme-updater-admin.php 83: include( dirname( __FILE__ ) . '/theme-updater-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 : index-switcher.php 14: include( get_template_directory() . '/inc/style-configurator/colors.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