52
Validation results

Uplift

Uplift

WordPress 4.9.8 theme
52
  • THEME TYPEWordPress theme 4.9.8
  • FILE NAMEuplift.zip
  • FILE SIZE6067682 bytes
  • MD5e623ae521754b74980c4400b2871a672
  • SHA19886e8dc5ec86cfc24166398609c51b14d8cb5b4
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEMEFOREST PAGEhttps://themeforest.net/item/uplift-responsive-multipurpose-wordpress-theme/15409157 ($59)
  • THEME URIhttp://uplift.swiftideas.com
  • VERSION1.3.76
  • TAGStranslation-ready, threaded-comments, theme-options, sticky-post, post-formats, full-width-template, flexible-header, featured-images, custom-menu, custom-header, custom-colors, custom-background, responsive-layout
  • CREATION DATE2018-07-27
  • LAST FILE UPDATE2018-07-27
  • LAST VALIDATION2018-07-27 15:30
  • OTHER VERSIONS

    1.3.14 : 32%

Critical alerts
  1. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe [^>]*src=")? # If iframe match up to first quote of src (?: # Group vimeo url https?:\/\/ # Either http or https (?:[\w]+\.)* # Optional subdomains vimeo\.com # Match vimeo.com (?:[\/\w]*\/videos?)? # Optional video sub directory this handles groups links also \/ # Slash before Id ([0-9]+) # $1: VIDEO_ID is numeric [^\s]* # Not a space ) # End group "? # Match end quote if part of src (?:[^> in file sf-media.php.
  2. Admin menu : Themes should use add_theme_page() for adding admin pages. File sf-options.php :
    Line 3935: 'page_parent'        	=> 'themes.php', // For a full list of options, visit: http://codex.wordpress.org/Function_Reference/add_submenu_page#Parameters
Warning
  1. theme tags : Presence of bad theme tagsThe tag responsive-layout has been deprecated, it must be removed from 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 'swiftframework' in file review.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 uplift, tgmpa, redux-framework, wpex, swiftideas, swift-framework-plugin, twentysixteen, meta-box, swiftframework, p, yith-woocommerce-wishlist, woocommerce.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  5. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  6. I18N implementation : Proper use of ___all(Possible variable $this found in translation function in sf-options.php. Translation function calls should not contain PHP variables.
    Line 3959: 'help_sidebar'       	=> '', // __( '', $this->args['domain'] );
  7. Date and time implementation : Use of the_time()At least one hard coded date was found in the file sf-page-heading.php. Function get_option( 'date_format' ) should be used instead.
  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 sf-head.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 home template file home.phpThis theme does not contain optional file home.php.
  5. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  6. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  7. Use of includes : Use of include or requireThe theme appears to use include or require : custom_css.php
    Line 27: require( $customizer_path . '/variables.php' );
    Line 95: require( $customizer_path . '/variables.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
    Line 217: require_once( ABSPATH . 'wp-admin/includes/file.php' );
    Line 264: require_once( ABSPATH . 'wp-admin/includes/file.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 : customizer.php
    Line 48: require_once( $customizer_path . '/sanitization.php' );
    Line 49: require_once( $customizer_path . '/custom_css.php' );
    Line 50: require_once( $customizer_path . '/output.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 : extension_widget_areas.php
    Line 60: require_once( dirname( __FILE__ ) . '/class.redux_widget_areas.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
    Line 15: require_once( get_template_directory() .'/includes/option-extensions/loader
    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 : loader.php
    Line 20: require_once( $class_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 : aq_resizer.php
    Line 21: require( get_template_directory() . '/includes/plugins/aq_resizer-2x.php' )
    Line 29: require( get_template_directory() . '/includes/plugins/aq_resizer-1x.php' )
    Line 32: require( get_template_directory() . '/includes/plugins/aq_resizer-1x.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 : love-it-pro.php
    Line 33: include(LI_BASE_DIR . '/includes/display-functions.php');
    Line 34: include(LI_BASE_DIR . '/includes/love-functions.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 : swift-framework.php
    Line 14: include_once( SF_FRAMEWORK_PATH . '/core/sf-base.php' );
    Line 15: include_once( SF_FRAMEWORK_PATH . '/core/sf-breadcrumbs.php' );
    Line 16: include_once( SF_FRAMEWORK_PATH . '/core/sf-comments.php' );
    Line 17: include_once( SF_FRAMEWORK_PATH . '/core/sf-footer.php' );
    Line 18: include_once( SF_FRAMEWORK_PATH . '/core/sf-formatting.php' );
    Line 19: include_once( SF_FRAMEWORK_PATH . '/core/sf-functions.php' );
    Line 20: include_once( SF_FRAMEWORK_PATH . '/core/sf-get-template.php' );
    Line 21: include_once( SF_FRAMEWORK_PATH . '/core/sf-head.php' );
    Line 22: include_once( SF_FRAMEWORK_PATH . '/core/sf-header.php' );
    Line 23: include_once( SF_FRAMEWORK_PATH . '/core/sf-media.php' );
    Line 24: include_once( SF_FRAMEWORK_PATH . '/core/sf-menus.php' );
    Line 25: include_once( SF_FRAMEWORK_PATH . '/core/sf-page-heading.php' );
    Line 26: include_once( SF_FRAMEWORK_PATH . '/core/sf-pagination.php' );
    Line 27: include_once( SF_FRAMEWORK_PATH . '/core/sf-directory.php' );
    Line 29: include_once( SF_FRAMEWORK_PATH . '/core/sf-supersearch.php' );
    Line 31: include_once( SF_FRAMEWORK_PATH . '/core/sf-woocommerce.php' );
    Line 36: include_once( SF_FRAMEWORK_PATH . '/content/sf-blog.php' );
    Line 37: include_once( SF_FRAMEWORK_PATH . '/content/sf-campaign-detail.php' );
    Line 38: include_once( SF_FRAMEWORK_PATH . '/content/sf-galleries.php' );
    Line 39: include_once( SF_FRAMEWORK_PATH . '/content/sf-pageslider.php' );
    Line 40: include_once( SF_FRAMEWORK_PATH . '/content/sf-portfolio.php' );
    Line 41: include_once( SF_FRAMEWORK_PATH . '/content/sf-portfolio-detail.php' );
    Line 42: include_once( SF_FRAMEWORK_PATH . '/content/sf-post-detail.php' );
    Line 43: include_once( SF_FRAMEWORK_PATH . '/content/sf-post-formats.php' );
    Line 44: include_once( SF_FRAMEWORK_PATH . '/content/sf-products.php' );
    Line 49: include_once( SF_FRAMEWORK_PATH . '/sf-megamenu/sf-megamenu.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 : sf-functions.php
    Line 555: require_once( ABSPATH . 'wp-admin/includes/file.php' );
    Line 1901: require_once( ABSPATH . 'wp-admin' . '/includes/image.php' );
    Line 1902: require_once( ABSPATH . 'wp-admin' . '/includes/file.php' );
    Line 1903: 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 : sf-megamenu.php
    Line 452: include_once( 'edit_custom_walker.php' );
    Line 453: include_once( 'mega_menu_custom_walker.php' );
    Line 454: include_once( 'alt_menu_custom_walker.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.

This is a ThemeForest theme. Since Themeforest items are all checked by a human before they appear on their website, ThemeForest verification rules are more permissive than themecheck's and can give a better verification score ( Themeforest requirements ).

95
  • THEME TYPEWordPress theme 4.9.8
  • FILE NAMEuplift.zip
  • FILE SIZE6067682 bytes
  • MD5e623ae521754b74980c4400b2871a672
  • SHA19886e8dc5ec86cfc24166398609c51b14d8cb5b4
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEMEFOREST PAGEhttps://themeforest.net/item/uplift-responsive-multipurpose-wordpress-theme/15409157 ($59)
  • THEME URIhttp://uplift.swiftideas.com
  • VERSION1.3.76
  • TAGStranslation-ready, threaded-comments, theme-options, sticky-post, post-formats, full-width-template, flexible-header, featured-images, custom-menu, custom-header, custom-colors, custom-background, responsive-layout
  • CREATION DATE2018-07-27
  • LAST FILE UPDATE2018-07-27
  • LAST VALIDATION2018-07-27 15:30
  • OTHER VERSIONS

    1.3.14 : 32%

Warning
  1. theme tags : Presence of bad theme tagsThe tag responsive-layout has been deprecated, it must be removed from 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 'swiftframework' in file review.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 uplift, tgmpa, redux-framework, wpex, swiftideas, swift-framework-plugin, twentysixteen, meta-box, swiftframework, p, yith-woocommerce-wishlist, woocommerce.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Date and time implementation : Use of the_time()At least one hard coded date was found in the file sf-page-heading.php. Function get_option( 'date_format' ) should be used instead.
  5. 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 sf-head.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 home template file home.phpThis theme does not contain optional file home.php.
  5. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  6. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  7. Use of includes : Use of include or requireThe theme appears to use include or require : custom_css.php
    Line 27: require( $customizer_path . '/variables.php' );
    Line 95: require( $customizer_path . '/variables.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
    Line 217: require_once( ABSPATH . 'wp-admin/includes/file.php' );
    Line 264: require_once( ABSPATH . 'wp-admin/includes/file.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 : customizer.php
    Line 48: require_once( $customizer_path . '/sanitization.php' );
    Line 49: require_once( $customizer_path . '/custom_css.php' );
    Line 50: require_once( $customizer_path . '/output.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 : extension_widget_areas.php
    Line 60: require_once( dirname( __FILE__ ) . '/class.redux_widget_areas.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
    Line 15: require_once( get_template_directory() .'/includes/option-extensions/loader
    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 : loader.php
    Line 20: require_once( $class_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 : aq_resizer.php
    Line 21: require( get_template_directory() . '/includes/plugins/aq_resizer-2x.php' )
    Line 29: require( get_template_directory() . '/includes/plugins/aq_resizer-1x.php' )
    Line 32: require( get_template_directory() . '/includes/plugins/aq_resizer-1x.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 : love-it-pro.php
    Line 33: include(LI_BASE_DIR . '/includes/display-functions.php');
    Line 34: include(LI_BASE_DIR . '/includes/love-functions.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 : swift-framework.php
    Line 14: include_once( SF_FRAMEWORK_PATH . '/core/sf-base.php' );
    Line 15: include_once( SF_FRAMEWORK_PATH . '/core/sf-breadcrumbs.php' );
    Line 16: include_once( SF_FRAMEWORK_PATH . '/core/sf-comments.php' );
    Line 17: include_once( SF_FRAMEWORK_PATH . '/core/sf-footer.php' );
    Line 18: include_once( SF_FRAMEWORK_PATH . '/core/sf-formatting.php' );
    Line 19: include_once( SF_FRAMEWORK_PATH . '/core/sf-functions.php' );
    Line 20: include_once( SF_FRAMEWORK_PATH . '/core/sf-get-template.php' );
    Line 21: include_once( SF_FRAMEWORK_PATH . '/core/sf-head.php' );
    Line 22: include_once( SF_FRAMEWORK_PATH . '/core/sf-header.php' );
    Line 23: include_once( SF_FRAMEWORK_PATH . '/core/sf-media.php' );
    Line 24: include_once( SF_FRAMEWORK_PATH . '/core/sf-menus.php' );
    Line 25: include_once( SF_FRAMEWORK_PATH . '/core/sf-page-heading.php' );
    Line 26: include_once( SF_FRAMEWORK_PATH . '/core/sf-pagination.php' );
    Line 27: include_once( SF_FRAMEWORK_PATH . '/core/sf-directory.php' );
    Line 29: include_once( SF_FRAMEWORK_PATH . '/core/sf-supersearch.php' );
    Line 31: include_once( SF_FRAMEWORK_PATH . '/core/sf-woocommerce.php' );
    Line 36: include_once( SF_FRAMEWORK_PATH . '/content/sf-blog.php' );
    Line 37: include_once( SF_FRAMEWORK_PATH . '/content/sf-campaign-detail.php' );
    Line 38: include_once( SF_FRAMEWORK_PATH . '/content/sf-galleries.php' );
    Line 39: include_once( SF_FRAMEWORK_PATH . '/content/sf-pageslider.php' );
    Line 40: include_once( SF_FRAMEWORK_PATH . '/content/sf-portfolio.php' );
    Line 41: include_once( SF_FRAMEWORK_PATH . '/content/sf-portfolio-detail.php' );
    Line 42: include_once( SF_FRAMEWORK_PATH . '/content/sf-post-detail.php' );
    Line 43: include_once( SF_FRAMEWORK_PATH . '/content/sf-post-formats.php' );
    Line 44: include_once( SF_FRAMEWORK_PATH . '/content/sf-products.php' );
    Line 49: include_once( SF_FRAMEWORK_PATH . '/sf-megamenu/sf-megamenu.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 : sf-functions.php
    Line 555: require_once( ABSPATH . 'wp-admin/includes/file.php' );
    Line 1901: require_once( ABSPATH . 'wp-admin' . '/includes/image.php' );
    Line 1902: require_once( ABSPATH . 'wp-admin' . '/includes/file.php' );
    Line 1903: 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 : sf-megamenu.php
    Line 452: include_once( 'edit_custom_walker.php' );
    Line 453: include_once( 'mega_menu_custom_walker.php' );
    Line 454: include_once( 'alt_menu_custom_walker.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