0
Validation results

Today (shared on wplocker.com)

Today (shared on wplocker.com)

WordPress 4.9.1 theme
0
    Error 8 : Undefined index: slug
    In /home/www/themecheck/themecheck/controllers/controller_results.php line 772
  • THEME TYPEWordPress theme 4.9.1
  • FILE NAMEtoday.zip
  • FILE SIZE1813076 bytes
  • MD5a67edcd9fc195c700d1fcbc4f32248a1
  • SHA144f9999f866da3883bddfbc26ce57711cfa8d567
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttp://today.wizedesign.com
  • VERSION1.5
  • AUTHOR URI
  • CREATION DATE2016-03-14
  • LAST FILE UPDATE2017-05-18
  • LAST VALIDATION2017-05-18 02:30
  • OTHER VERSIONS

    1.3 : 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.
    Line 202: $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-soundcloud.php.
    Line 37: <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 soundcloud.php.
    Line 142: return sprintf('<iframe width='%s' height='%s' scrolling='no' frameborder='no' src='%s'></i
    Found <iframe src="http://player.vimeo.com/video/' . $vimeo . '" width="650" height="380" frameborder="0" allowFullScreen> in file video.php.
    Line 8: <iframe src='http://player.vimeo.com/video/' . $vimeo . '' width='650' heig
  5. Malware : Operations on file system readfile was found in the file download-image.php
    Line 12: readfile($file);
  6. Malware : Network operations curl_init was found in the file twitteroauth.php
    Line 195: $ci = curl_init();
    curl_exec was found in the file twitteroauth.php
    Line 221: $response = curl_exec($ci);
  7. Admin menu : Themes should use add_theme_page() for adding admin pages. File options-framework.php :
    Line 168: $of_page = add_menu_page(
  8. Deprecated functions : get_the_author_ID get_the_author_ID found in file author.php. Deprecated since version 2.8. Use get_the_author_meta(&#39;ID&#39;) instead.
    Line 5: $aut = get_the_author_ID();
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 today-shared-on-wplocker-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.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 wizedesign, clubber, , 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 license urlLicense URI: is missing from style.css header.
  9. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  10. 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.
  11. Screenshot : Screenshot fileScreenshot size is 600x450px. 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.
    Line 217: <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.
    Line 91: ?>'>Flickr ID (<a href='http://www.idgettr.com' target='_blank'>idGettr</a>):</label>
    Possible hard-coded links were found in the file soundcloud.php.
    Line 171: $settings_link = '<a href='options-general.php?page=soundcloud-shortcode'>Settings</a>';
    Possible hard-coded links were found in the file options-framework.php.
    Line 242: <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 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 : blog-style1.php
    Line 68: require('slider.php');
    Line 72: require('feature.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 : header.php
    Line 92: require('banner.php');
    Line 131: require('breaking-news.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
    Line 39: @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 : twitteroauth.php
    Line 10: 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 : footer.php
    Line 108: require('js/JSscript.php');
    Line 109: require('js/JSprettyPhoto.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 : blog-style2.php
    Line 68: require('slider.php');
    Line 72: require('feature.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.php
    Line 56: require('slider.php');
    Line 60: require('feature.php');
    Line 120: require('start-page.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.php
    Line 95: require('admin/video.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 : blog-style3.php
    Line 68: require('slider.php');
    Line 72: require('feature.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
    Line 73: 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
    Line 19: 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 : css_options.php
    Line 3: 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 : start-page.php
    Line 8: require('slider.php');
    Line 12: require('feature.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 : blog-style4.php
    Line 70: require('slider.php');
    Line 74: require('feature.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