0
Validation results

domipravo.ru

domipravo.ru

WordPress 4.9.8 theme
0
  • THEME TYPEWordPress theme 4.9.8
  • FILE NAMEdomipravo.ru.zip
  • FILE SIZE3346500 bytes
  • MD5f4d45a89475e08622c5973c9e298a865
  • SHA16943bfc21016e9476e9cb80ef975a0b3ae40b912
  • LICENSENone
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • VERSION2018.07.04.11.16
  • CREATION DATE2018-09-13
  • LAST FILE UPDATE2018-09-13
  • LAST VALIDATION2018-09-13 11:29
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_encode() Found base64_encode in file item_thumbnail.php.
     return 'data:image/png;base64,' . base64_encode($image);
  3. Unwanted files : hidden file(s) or folder(s) .gitignore .travis.yml .editorconfig was found.
  4. Malware : Operations on file system file_get_contents was found in the file kama_thumbnail.php
    Line 236: $expire = @file_get_contents($folder.'/expire');
    file_put_contents was found in the file kama_thumbnail.php
    Line 239: file_put_contents($folder.'/expire', time()+3600*24*3);
  5. Admin menu : Themes should use add_theme_page() for adding admin pages. File Theme_Options_Container.php :
    Line 161: add_menu_page(
    File Theme_Options_Container.php :
    Line 172: add_submenu_page(
  6. Content width : Proper definition of content_width No content width has been defined. Example:
    if ( ! isset( $content_width ) ) $content_width = 900;
  7. Deprecated functions : get_bloginfo get_bloginfo('template_url') was found in the file functions.php. Use get_template_directory_uri() instead.
    Line 38: wp_register_script('social-likes', get_bloginfo('template_url').'/js/social-likes.min.js', array('jquery'), nu
    Line 42: wp_register_script( 'scripts.js', get_bloginfo('template_url').'/js/scripts.js', array('jquery'), null, true 
  8. Deprecated functions : bloginfo bloginfo('url') was found in the file header.php. Use echo esc_url( home_url() ) instead.
    Line 28: <a class='header__logo' href='<?php bloginfo('url') ?>/'><?php echo $logo_text; ?></a>
    Line 84: <form class='search' method='get' action='<?php bloginfo('url') ?>/'>
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 domipravo-ru.
  3. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments 'F j, Y' in file Helper.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'The new version of Carbon Fields is a major update. Please make sure you have a full backup before updating and test any add-ons or custom functionality.', \n, 'Developers should review the upgrade guide on %1$s.' in file Plugin_Update_Warning.php.Found a translation function that has an incorrect number of arguments. Function __, with the arguments 'The new version of Carbon Fields is a major update. Please make sure you have a full backup before updating and test any add-ons or custom functionality.', \n, 'Developers should review the upgrade guide on %1$s.', 'carbon-fields' in file Plugin_Update_Warning.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Edit' in file functions.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Your comment is awaiting moderation.' in file functions.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Вы вошли как <a href="%1$s">%2$s</a>. <a href="%3$s" title="Выйти из этой учётной записи">Выйти &raquo;</a>' in file comments.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 carbon-fields, \n.
  4. Plugin territory : Plugin territory functionalitiesThe theme uses the register_post_type() function, which is plugin-territory functionality.
  5. Unwanted directories : GIT revision control directoryGIT revision control directory.git was found.
  6. PHP short tags : Presence of PHP short tagsPHP short tags were found in file wp-config.php. "This practice is discouraged because they are only available if enabled with short_open_tag php.ini configuration file directive, or if PHP was configured with the --enable-short-tags option" (php.net), which is not the case on many servers.
    Line 56: define('NONCE_SALT',       'h;PT|1M%X<?j;uym sD_g~uW`H_NLz>L+ O&wxiwctUmPx9m;N%v1m.2f$nk9g|]');
  7. Fundamental theme elements : Presence of add_theme_support()Could not find add_theme_support( 'automatic-feed-links' ).
  8. Fundamental theme elements : Presence of comment_form()Could not find comment_form.
  9. Fundamental theme elements : Presence of body_class()Could not find body_class call in body tag.
  10. Fundamental theme elements : Presence of wp_link_pages()Could not find wp_link_pages.
  11. Fundamental theme elements : Presence of post_class()Could not find post_class.
  12. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  13. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  14. I18N implementation : Proper use of ___all(Possible variable $this found in translation function in Complex_Field.php. Translation function calls should not contain PHP variables.
    Line 113: 'singular_name' => __( $this->labels['singular_name'], 'carbon-fields' ),
    Possible variable $this found in translation function in Complex_Field.php. Translation function calls should not contain PHP variables.
    Line 114: 'plural_name' => __( $this->labels['plural_name'], 'carbon-fields' ),
  15. Featured image : Use of the_post_thumbnail() instead of custom fields for thumbnailsNo reference to the_post_thumbnail was found in the theme.
  16. CSS files : Presence of license typeLicense: is missing from style.css header.
  17. CSS files : Presence of license urlLicense URI: is missing from style.css header.
  18. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  19. CSS files : Presence of .sticky class.sticky css class is needed in theme css.
  20. CSS files : Presence of .bypostauthor class.bypostauthor css class is needed in theme css.
  21. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
  22. 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.
  23. CSS files : Presence of Theme URICould not find Theme URL.
  24. CSS files : Presence of Author URICould not find Author URI.
  25. Tags : Tags displayThis theme doesn't seem to display tags.
  26. Date and time implementation : Use of the_time()At least one hard coded date was found in the file __item-news.php. Function get_option( 'date_format' ) should be used instead.At least one hard coded date was found in the file home.php. Function get_option( 'date_format' ) should be used instead.
  27. Screenshot : Screenshot fileScreenshot dimensions are wrong! Detected: 700x700px (1:1). Ratio of width to height should be 4:3.Screenshot size is 700x700px. 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 category template file category.phpThis theme does not contain optional file category.php.
  4. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  5. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  6. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  7. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  8. Optional files : Presence of archive template file archive.phpThis theme does not contain optional file archive.php.
  9. Optional files : Presence of search results template file search.phpThis theme does not contain optional file search.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 : header.php
    Line 10: require_once 'includes/crb_theme-vars.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 : Loader.php
    Line 40: include_once( dirname( dirname( __DIR__ ) ) . '/config.php' );
    Line 41: include_once( \Carbon_Fields\DIR . '/core/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 : network.php
    Line 3: require( 'common/options-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 : theme_options.php
    Line 3: require( 'common/options-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 : carbon-fields-plugin.php
    Line 23: require( __DIR__ . '/vendor/autoload.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.php
    Line 1: <?php require('header.php') ?>
    Line 25: <?php include '__item-big.php'; ?>
    Line 42: <?php include '__item.php'; ?>
    Line 68: <?php require('sidebar.php') ?>
    Line 70: <?php require('footer.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 : home.php
    Line 1: <?php require('header.php') ?>
    Line 26: <?php include '__item-big.php'; ?>
    Line 50: <?php include '__item-small.php'; ?>
    Line 59: <?php include '__questions.php'; ?>
    Line 148: <?php include '__item.php'; ?>
    Line 159: <?php include '__vk-widget.php'; ?>
    Line 166: <?php include '__phones.php'; ?>
    Line 186: <?php require('footer.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 : yarpp-template-related.php
    Line 13: include '__item.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 : sidebar.php
    Line 8: include '__questions.php';
    Line 11: <?php include '__phones.php'; ?>
    Line 23: <?php include '__item-expert.php'; ?>
    Line 29: <?php include '__vk-widget.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 1: <?php require('header.php'); ?>
    Line 17: <?php require('sidebar.php'); ?>
    Line 18: <?php require('footer.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 1: <?php require('header.php'); ?>
    Line 52: <?php require('sidebar.php'); ?>
    Line 54: <?php require('footer.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 : __questions.php
    Line 24: <?php include '__item-expert.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 : wp-config.php
    Line 88: require_once(ABSPATH . 'wp-settings.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 : 404.php
    Line 1: <?php require('header.php'); ?>
    Line 10: <?php require('sidebar.php'); ?>
    Line 11: <?php require('footer.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