0
Validation results

SW Theme

SW Theme

WordPress 5.2.4 theme
0
  • THEME TYPEWordPress theme 5.2.4
  • FILE NAMEnorcalpool.zip
  • FILE SIZE3910596 bytes
  • MD520f1266690adbc7a2161844eb5599dcc
  • SHA1211b45e0ff6ca6d1a75f5e415bbfc295b53349dc
  • LICENSENone
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttp://www.sweans.com
  • VERSION2.0
  • AUTHOR URI
  • CREATION DATE2019-10-01
  • LAST FILE UPDATE2019-10-01
  • LAST VALIDATION2019-10-01 06:21
  • OTHER VERSIONS

    4.1.0 : 51%

This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Title : Title The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
  2. Malware : Operations on file system file_get_contents was found in the file field_groups.php 378: $items = file_get_contents( $path . 'readme.txt' );
  3. Admin menu : Themes should use add_theme_page() for adding admin pages. File acf.php : 603: add_menu_page(__('Custom Fields','acf'), __('Custom Fields','acf'), 'manageFile addons.php : 42: $page = add_submenu_page('edit.php?post_type=acf', __('Add-ons','acf'), __('Add-onsFile export.php : 50: $page = add_submenu_page('edit.php?post_type=acf', __('Export','acf'), __('Export',File upgrade.php : 77: add_submenu_page('edit.php?post_type=acf', __('Upgrade','acf'), __('Upgrade
  4. Comment reply : Declaration of comment reply Could not find the comment-reply js script enqueued.
  5. Deprecated functions : bloginfo bloginfo('url') was found in the file searchform.php. Use echo esc_url( home_url() ) instead.1: <form method='get' id='searchform' action='<?php bloginfo('url'); ?>/'>bloginfo('template_directory') was found in the file footer.php. Use echo esc_url( get_template_directory_uri() ) instead.11: <img src='<?php bloginfo('template_directory')?>/images/swlogo.png' alt='Sweans Digital Mar
  6. Search form : Implementation File search.php :33: Use get_search_form() instead of including searchform.php directly.File index.php :43: Use get_search_form() instead of including searchform.php directly.
Warning
  1. special URIs : Presence of bad theme tagsTheme URI and Author URI should not be the same.
  2. theme tags : Presence of bad theme tagsFound wrong tag in style.css header.
  3. 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 sw-theme.
  4. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments "Title" in file field_groups.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'acf' in file upgrade.php.Found a translation function that is missing a text-domain. Function __, with the arguments 'Dummy' in file dummy.php.Found a translation function that is missing a text-domain. Function _e, with the arguments in file comments.php.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Recent Posts' in file leftsidebar.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 acf, theme-text-domain, option-tree-theme, option-tree, sw theme, norcalpool.
  5. 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.
  6. Fundamental theme elements : Presence of wp_list_comments()Could not find wp_list_comments.
  7. Fundamental theme elements : Presence of comment_form()Could not find comment_form.
  8. Fundamental theme elements : Presence of post_class()Could not find post_class.
  9. 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.
  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. I18N implementation : Proper use of _e(Possible variable $numPingBacks found in translation function in comments.php. Translation function calls should not contain PHP variables.
  14. I18N implementation : Proper use of ___all(Possible variable $wp_postmeta found in translation function in upgrade.php. Translation function calls should not contain PHP variables.
  15. CSS files : Presence of license urlLicense URI: is missing from style.css header.
  16. CSS files : Presence of text domainText Domain: is missing from your style.css header.
  17. CSS files : Presence of .sticky class.sticky css class is needed in theme css.
  18. CSS files : Presence of .bypostauthor class.bypostauthor css class is needed in theme css.
  19. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
  20. 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.
  21. Date and time implementation : Use of the_time()At least one hard coded date was found in the file sidebar.php. Function get_option( 'date_format' ) should be used instead.
  22. Screenshot : Screenshot fileScreenshot is wrong size! Detected: 1200x1166px. Maximum allowed size is 1200x900px.Screenshot dimensions are wrong! Detected: 1200x1166px (600:583). Ratio of width to height should be 4:3.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 addons.php.201: <p><strong><?php _e('Just updated to version 4?','acf'); ?></strong> <?php _e('Activation codes have changed to plugins! Download your purchased add-ons','acf'); ?> <a href='http://www.advancedcustomfields.com/add-ons-download/' target='_blank'><?phPossible hard-coded links were found in the file field_groups.php.345: <?php printf(__('Migrating your field types is easy, please %sfollow this tutorial%s to learn more.','acf'),'<a href='http://www.advancedcustomfields.com/docs/tutorials/creating-a-new-field-typ348: <p><?php printf(__('All actions & filters have received a major facelift to make customizing ACF even easier! Please %sread this guide%s to find the updated naming convention.','acf'),'<a href='http://www.advancedcustomfields.com/resources/getting-started/migrating-fro361: <p><?php printf(__('Due to the sizable changes surrounding Add-ons, field types and action/filters, your website may not operate correctly. It is important that you read the full %sMigrating from v3 to v4%s guide to view the full list of changes.','acf'),'<a href='http://www.advancedcustomfields.com/resources/getting-started/migrating-fro348: <p><?php printf(__('All actions & filters have received a major facelift to make customizing ACF even easier! Please %sread this guide%s to find the updated naming convention.','acf'),'<a href='http://www.advancedcustomfields.com/resources/getting-started/migrating-fro361: <p><?php printf(__('Due to the sizable changes surrounding Add-ons, field types and action/filters, your website may not operate correctly. It is important that you read the full %sMigrating from v3 to v4%s guide to view the full list of changes.','acf'),'<a href='http://www.advancedcustomfields.com/resources/getting-started/migrating-froPossible hard-coded links were found in the file date_picker.php.128: <p><?php _e('\'yymmdd\' is the most versatile save format. Read more about','acf'); ?> <a href='http://docs.jquery.com/UI/Datepicker/formatDate'><?php _e('jQuery date form144: <p><?php _e('\'dd/mm/yy\' or \'mm/dd/yy\' are the most used display formats. Read more about','acf'); ?> <a href='http://docs.jquery.com/UI/Datepicker/formatDate' target='_blank'><?php _e('128: <p><?php _e('\'yymmdd\' is the most versatile save format. Read more about','acf'); ?> <a href='http://docs.jquery.com/UI/Datepicker/formatDate'><?php _e('jQuery date form144: <p><?php _e('\'dd/mm/yy\' or \'mm/dd/yy\' are the most used display formats. Read more about','acf'); ?> <a href='http://docs.jquery.com/UI/Datepicker/formatDate' target='_blank'><?php _e('Possible hard-coded links were found in the file sidebar.php.53: <li><a href='http://validator.w3.org/check/referer' title='This page validates as XHTML 54: <li><a href='http://gmpg.org/xfn/'><abbr title='XHTML Friends Network'>XFN</abbr></a></lPossible hard-coded links were found in the file footer.php.9: <div class='sw_copy'>Site designed by <a href='http://www.sweans.com/' target='_blank'>Sweans Technologies</a></div>
  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 author template file author.phpThis theme does not contain optional file author.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. Use of includes : Use of include or requireThe theme appears to use include or require : search.php 33: <?php include (TEMPLATEPATH . '/searchform.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 : acf.php 372: include_once('core/api.php');374: include_once('core/controllers/input.php');375: include_once('core/controllers/location.php');376: include_once('core/controllers/field_group.php');382: include_once('core/controllers/post.php');383: include_once('core/controllers/revisions.php');384: include_once('core/controllers/everything_fields.php'); 385: include_once('core/controllers/field_groups.php');390: include_once('core/fields/_functions.php');391: include_once('core/fields/_base.php');393: include_once('core/fields/text.php');394: include_once('core/fields/textarea.php');395: include_once('core/fields/number.php');396: include_once('core/fields/email.php');397: include_once('core/fields/password.php');399: include_once('core/fields/wysiwyg.php');400: include_once('core/fields/image.php');401: include_once('core/fields/file.php');403: include_once('core/fields/select.php');404: include_once('core/fields/checkbox.php');405: include_once('core/fields/radio.php');406: include_once('core/fields/true_false.php');408: include_once('core/fields/page_link.php');409: include_once('core/fields/post_object.php');410: include_once('core/fields/relationship.php');411: include_once('core/fields/taxonomy.php');412: include_once('core/fields/user.php');414: include_once('core/fields/google-map.php');415: include_once('core/fields/date_picker/date_picker.php');416: include_once('core/fields/color_picker.php');418: include_once('core/fields/message.php');419: include_once('core/fields/tab.php');481: include_once('core/controllers/export.php');482: include_once('core/controllers/addons.php');483: include_once('core/controllers/third_party.php');484: include_once('core/controllers/upgrade.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 : field_group.php 417: include( $this->settings['path'] . 'core/views/meta_box_fields.php' );431: include( $this->settings['path'] . 'core/views/meta_box_location.php' );445: include( $this->settings['path'] . 'core/views/meta_box_options.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 : export.php 93: include_once($path . 'core/actions/export.php');320: include_once('advanced-custom-fields/acf.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 : dummy.php 276: include_once('fields/dummy.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 : user.php 126: require_once( ABSPATH . '/wp-admin/includes/user.php' ); 148: require_once( ABSPATH . '/wp-admin/includes/user.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 : demo-functions.php 65: # require( trailingslashit( get_template_directory() ) . 'option-tree/ot-load70: # require( trailingslashit( get_template_directory() ) . 'admin/theme-options 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 : ot-loader.php 553: include_once( $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 : ot-functions-docs-page.php 751: require( trailingslashit( get_template_directory() ) . \'includes/meta-boxe834: require( trailingslashit( get_template_directory() ) . \'option-tree/ot-loa851: require( trailingslashit( get_template_directory() ) . \'includes/theme-opt 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 43: <?php include (TEMPLATEPATH . '/searchform.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