0
Validation results

Clubber [Shared By http://www.themes24x7.com/]

Clubber [Shared By http://www.themes24x7.com/]

WordPress 4.8.2 theme
0
    Error 8 : Undefined index: slug
    In /home/www/themecheck/themecheck/controllers/controller_results.php line 772
  • THEME TYPEWordPress theme 4.8.2
  • FILE NAMEclubber.zip
  • FILE SIZE1729550 bytes
  • MD5ca298919ed41a7b4a54970de6b531b19
  • SHA140f74938435bb95ec5d6e39a1383e5749d7172d2
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttp://clubber.wizedesign.com
  • VERSION2.5.2
  • AUTHOR URI
  • CREATION DATE2016-08-12
  • LAST FILE UPDATE2017-03-07
  • LAST VALIDATION2017-03-07 01:25
  • OTHER VERSIONS

    2.6.1 : 0%

    1.8 : 0%

Critical alerts
  1. 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.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 OAuth.php.
    Ligne202: $decoded_sig = base64_decode($signature);
  3. Security breaches : Use of base64_encode() Found base64_encode in file OAuth.php.
     return base64_encode(hash_hmac('sha1', $base_string, $key, true));
     return base64_encode($signature);
  4. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe width="100%" height="166" scrolling="no" frameborder="no" src="http://w.soundcloud.com/player/?url=http%3A%2F%2Fapi.soundcloud.com%2Ftracks%2F' . $soundcloud . '&show_artwork=true"> in file widget-audio.php.
    Ligne155: <iframe width='100%' height='166' scrolling='no' frameborder='no' src='http
    Found <iframe width="100%" height="166" scrolling="no" frameborder="no" src="http://w.soundcloud.com/player/?url=http%3A%2F%2Fapi.soundcloud.com%2Ftracks%2F' . $soundcloud . '&show_artwork=true"> in file widget-soundcloud.php.
    Ligne37: <iframe width='100%' height='166' scrolling='no' frameborder='no' src='http
    Found <iframe width="%s" height="%s" scrolling="no" frameborder="no" src="%s"> in file shortcode-soundcloud.php.
    Ligne142: return sprintf('<iframe width='%s' height='%s' scrolling='no' frameborder='no' src='%s'></i
  5. Malware : Operations on file system file_get_contents was found in the file OAuth.php
    Ligne272: file_get_contents(self::$POST_INPUT)
    readfile was found in the file download-image.php
    Ligne12: readfile($file);
  6. Malware : Network operations curl_init was found in the file twitteroauth.php
    Ligne195: $ci = curl_init();
    curl_exec was found in the file twitteroauth.php
    Ligne221: $response = curl_exec($ci);
  7. Admin menu : Themes should use add_theme_page() for adding admin pages. File options-framework.php :
    Ligne168: $of_page = add_menu_page(
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag in style.css header.
  2. Text domain : Incorrect use of translation functions.Wrong installation directory for the theme name. The directory name must match the slug of the theme. This theme's correct slug and text-domain is clubber-shared-by-httpwww-themes24x7-com.
  3. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments 'Archive' in file header.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'Add New', clubber, 'clubber' in file photo.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 clubber, , wizedesign, gxg_textdomain, optionsframework.
  4. 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.
  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. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  9. CSS files : Presence of .screen-reader-text class.screen-reader-text css class is needed in your theme css. See : the Codex for an example implementation.
  10. Screenshot : Screenshot fileScreenshot size is 880x660px. 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. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file widget-twitter.php.
    Ligne217: <p>You can sign up for a API key <a href='https://dev.twitter.com/' target='_blank'>here</a></small></p>
    Possible hard-coded links were found in the file widget-flickr.php.
    Ligne91: ?>'>Flickr ID (<a href='http://www.idgettr.com' target='_blank'>idGettr</a>):</label>
    Possible hard-coded links were found in the file shortcode-soundcloud.php.
    Ligne171: $settings_link = '<a href='options-general.php?page=soundcloud-shortcode'>Settings</a>';
    Possible hard-coded links were found in the file options-framework.php.
    Ligne242: <a href='http://wizedesign.com' target='_blank'><div class='logo'></div></a>
  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 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 attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  11. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  12. Use of includes : Use of include or requireThe theme appears to use include or require : language.php
    Ligne6: require('language/EN.php');
    Ligne10: require('language/RO.php');
    Ligne14: require('language/ES.php');
    Ligne18: require('language/IT.php');
    Ligne22: require('language/PT.php');
    Ligne26: require('language/DE.php');
    Ligne30: require('language/NL.php');
    Ligne34: require('language/FR.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 : widget-twitter.php
    Ligne39: @require_once 'twitteroauth/twitteroauth.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 : widget-events.php
    Ligne55: require($theme.'/includes/language.php');
    Ligne213: require($theme.'/includes/language.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 : twitteroauth.php
    Ligne10: require_once('OAuth.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 : shortcode-posts.php
    Ligne132: require($theme.'/includes/language.php');
    Ligne273: require($theme.'/includes/language.php');
    Ligne414: require($theme.'/includes/language.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 : single-event.php
    Ligne54: require('includes/language.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 : events-style1past.php
    Ligne87: require('includes/language.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 : events-style2.php
    Ligne86: require('includes/language.php');
    Ligne198: require('includes/language.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 : events-style3.php
    Ligne87: require('includes/language.php');
    Ligne206: require('includes/language.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 : options-framework.php
    Ligne73: require_once($optionsfile);
    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 : options.php
    Ligne19: require_once (OPTIONS_FRAMEWORK_URL . 'options-framework.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 : events-style1.php
    Ligne82: require('includes/language.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 : css_options.php
    Ligne2: require_once( '../../../../wp-load.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 : events-style1up.php
    Ligne87: require('includes/language.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