0
Validation results

Abito

Abito

WordPress 4.9.4 theme
0
  • THEME TYPEWordPress theme 4.9.4
  • FILE NAMEabito-v133.zip
  • FILE SIZE1772426 bytes
  • MD5dc099c565bc9483515ddc295953a2cb0
  • SHA1893aa299f0c264679225c6945532572773d210ba
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • THEME URIhttp://abito.fedeweb.net
  • VERSION1.3.3
  • AUTHOR URI
  • TAGSblog, grid, clean
  • CREATION DATE2017-09-29
  • LAST FILE UPDATE2017-09-29
  • LAST VALIDATION2017-09-29 19:02
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. Widgets : Widgets Sidebars need to be registered in a custom function hooked to the widgets_init action. See: register_sidebar().
  3. Unwanted files : hidden file(s) or folder(s) .ds_store .scrutinizer.yml .travis.yml .editorconfig was found.
  4. Admin menu : Themes should use add_theme_page() for adding admin pages. File class-tgm-plugin-activation.php :
    Line 621: $this->page_hook = call_user_func( 'add_submenu_page', $args['parent_slug'], $args['page_title'], $args['menu_t
    File premium.php :
    Line 55: add_menu_page($premiumname, '$premiumname', 'edit_themes', basename(__FILE_
    File theme-options.php :
    Line 481: add_menu_page($themename.' Options', ''.$themename.' Options', 'edit_themes
    File update_notifier.php :
    Line 14: add_dashboard_page( $theme_name . 'Theme Updates', $theme_name . '<span cla
  5. Content width : Proper definition of content_width No content width has been defined. Example:
    if ( ! isset( $content_width ) ) $content_width = 900;
  6. Deprecated functions : attribute_escape attribute_escape found in file widget.php. Deprecated since version 2.8. Use esc_attr() instead.
    Line 74: <p><label for='<?php echo $this->get_field_id('title'); ?>'>Title: <input class='widefat' id='<?php echo $this->get_field_id('title'); ?>' name='<?php echo $this->get_field_name('title'); ?>' type='text' value='<?php echo attribute_escape($title); ?>' /></label></p>
    Line 75: <p><label for='<?php echo $this->get_field_id('number'); ?>'>Number of posts to show (per category): <input id='<?php echo $this->get_field_id('number'); ?>' name='<?php echo $this->get_field_name('number'); ?>' type='text' value='<?php echo attribute_escape($number); ?>' /></label></p>
    attribute_escape found in file register-sidebar.php. Deprecated since version 2.8. Use esc_attr() instead.
    Line 28: $form .='<input type='text' value='' . attribute_escape(apply_filters('the_search_query', get_search_query())) . '
    Line 32: $form .= '<input type='submit' id='searchsubmit' value=''.attribute_escape(__('Go')).'' />
  7. Deprecated functions : get_bloginfo get_bloginfo( 'template_url' ) was found in the file update_notifier.php. Use get_template_directory_uri() instead.
    Line 39: <img style='float: left; margin: 0 20px 20px 0; border: 1px solid #ddd;' src='<?php echo get_bloginfo( 'template_url' ) . '/screenshot.png'; ?>' />
  8. Deprecated functions : get_option get_option('home') was found in the file register-sidebar.php. Use home_url() instead.
    Line 25: $form = '<form method='get' id='searchform' action='' . get_option('home') . '/' >
  9. Post pagination : Implementation The theme doesn't have post pagination code in it. Use posts_nav_link() or paginate_links() or the_posts_pagination() or the_posts_navigation() or next_posts_link() and previous_posts_link() to add post pagination.
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag grid in style.css header.Found wrong tag clean in 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 'Posts in the same category' in file widget.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Posts in the same category' in file widget.php.Found a translation function that is missing a text-domain. Function __, with the arguments '<cite class="fn">%s</cite>' in file comments.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Your comment is awaiting moderation.' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments '%1$s' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments '(Edit)' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Go' in file register-sidebar.php.Found a translation function that is missing a text-domain. Function __, with the arguments "Square" in file images_sizes.php.Found a translation function that is missing a text-domain. Function __, with the arguments "View all posts in %s" in file single.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Your name' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Your email' in file comments.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Website' in file comments.php.Found a translation function that is missing a text-domain. Function _x, with the arguments 'Comment', 'noun' 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 fw, tgmpa, ffg-one.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Fundamental theme elements : Presence of language_attributes()Could not find .
  5. Fundamental theme elements : Presence of add_theme_support()Could not find add_theme_support( 'automatic-feed-links' ).
  6. Fundamental theme elements : Presence of wp_link_pages()Could not find wp_link_pages.
  7. Fundamental theme elements : Presence of post_class()Could not find post_class.
  8. Comment pagination : Declaration of comment paginationThe theme doesn't have comment pagination code in it. Use paginate_comments_links() to add comment pagination, or older previous_comments_link() and next_comments_link() functions.
  9. Comment reply : Declaration of comment replyCould not find the comment-reply script enqueued, however a reference to 'comment-reply' was found. Make sure that the comment-reply js script is being enqueued properly on singular pages.
  10. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  11. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  12. 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.
  13. Featured image : Use of the_post_thumbnail() instead of custom fields for thumbnailsNo reference to the_post_thumbnail was found in the theme.
  14. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  15. CSS files : Presence of .sticky class.sticky css class is needed in theme css.
  16. CSS files : Presence of .bypostauthor class.bypostauthor css class is needed in theme css.
  17. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
  18. 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.
  19. 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 theme-options.php.
    Line 503: <p class='read-documentation'>Need help? View the <a href='http://abito.fedeweb.net/docs' target='_blank'>documentation</a> or send us
  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 term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  6. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  7. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  8. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  9. Use of includes : Use of include or requireThe theme appears to use include or require : tag.php
    Line 13: <?php include ('parts/shared/theme_options_loader.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 : archive.php
    Line 18: <?php include ('parts/shared/theme_options_loader.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 17: <?php include ('parts/shared/theme_options_loader.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 : search.php
    Line 13: <?php include ('parts/shared/theme_options_loader.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 18: <?php include ('parts/shared/theme_options_loader.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 : category.php
    Line 13: <?php include ('parts/shared/theme_options_loader.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 13: <?php include ('parts/shared/theme_options_loader.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 : metaboxes.php
    Line 8: require_once( 'fw_meta_box.php' );
    Line 19: //require_once('metaboxes/metaboxes_home.php');
    Line 20: //require_once('metaboxes/metaboxes_gallery.php');
    Line 21: //require_once('metaboxes/metaboxes_staff.php');
    Line 22: //require_once('metaboxes/metaboxes_contact.php');
    Line 23: //require_once('metaboxes/metaboxes_portfolio.php');
    Line 24: //require_once('metaboxes/metaboxes_common.php');
    Line 25: require_once('metaboxes/metaboxes_single.php');
    Line 26: require_once('metaboxes/metaboxes_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 : comments.php
    Line 15: <?php include ('parts/shared/theme_options_loader.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 1: <?php include ('theme_options_loader.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 1: <?php include ('theme_options_loader.php'); ?>
    Line 173: include ('infinite_scroll.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 : author.php
    Line 13: <?php include ('parts/shared/theme_options_loader.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 13: <?php include ('parts/shared/theme_options_loader.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