Whoa, I can not see how I spent good money here for this theme.. went to do the theme check and got these errors: REQUIRED:.screen-reader-text css class is needed in your theme css. See See: the Codex for an example implementation. WARNING: Your theme appears to be in the wrong directory for the theme name. The directory name must match the slug of the theme. This theme's correct slug and text-domain is colorway-pro-responsive-theme. WARNING: The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality. WARNING: The flexible-width and fixed-width tags changed to fluid-layout and fixed-layout tags in WordPress 3.8. Additionally, the responsive-layout tag was added. Please change to using one of the new tags. WARNING: Found wrong tag, remove full width from your style.css header. WARNING: Found PHP short tags in file contact.php. Line 79: <?= $nameError; ?> Line 88: <?= $emailError; ?> Line 105: <?= $commentError; ?> WARNING: Both DOS and UNIX style line endings were found in the file style.css. This causes a problem with SVN repositories and must be corrected before the theme can be accepted. Please change the file to use only one style of line endings. WARNING: dwsync.xml Dreamweaver project file found. REQUIRED: Could not find comment_form. See: comment_form <?php comment_form(); ?> REQUIRED: get_current_theme() found in the file functions/theme-options.php. Deprecated since version 3.4. Use wp_get_theme() instead. Line 8: $themename = function_exists('wp_get_theme') ? wp_get_theme() : get_current_theme(); REQUIRED: get_bloginfo('url') was found in the file functions.php. Use home_url() instead. Line 204: $homeLink = get_bloginfo('url'); REQUIRED: get_bloginfo('stylesheet_directory') was found in the file functions/theme-options.php. Use get_stylesheet_directory_uri() instead. Line 52: $imagepath = get_bloginfo('stylesheet_directory') . '/images/'; REQUIRED: get_bloginfo('home') was found in the file attachment.php. Use home_url() instead. Line 15: echo '<a href='' . get_bloginfo('home') . '' title='Home'>' . __('Home', 'colorway') . ' </a> REQUIRED: bloginfo('url') was found in the file header.php. Use echo esc_url( home_url() ) instead. Line 71: <a href='<?php bloginfo('url'); ?>'> REQUIRED: bloginfo('url') was found in the file functions.php. Use echo esc_url( home_url() ) instead. Line 204: $homeLink = get_bloginfo('url'); REQUIRED: bloginfo('template_url') was found in the file header.php. Use echo esc_url( get_template_directory_uri() ) instead. Line 61: echo bloginfo('template_url') . '/images/body-bg.png'; Line 76: echo bloginfo('template_url') . '/images/logo.png'; REQUIRED: bloginfo('template_directory') was found in the file functions.php. Use echo esc_url( get_template_directory_uri() ) instead. Line 703: <link rel='shortcut icon' href='<?php echo bloginfo('template_directory') ?>/images/favicon.ico' /> REQUIRED: bloginfo('stylesheet_directory') was found in the file functions/theme-options.php. Use echo esc_url( get_stylesheet_directory_uri() ) instead. Line 52: $imagepath = get_bloginfo('stylesheet_directory') . '/images/'; REQUIRED: bloginfo('home') was found in the file attachment.php. Use echo esc_url( home_url() ) instead. Line 15: echo '<a href='' . get_bloginfo('home') . '' title='Home'>' . __('Home', 'colorway') . ' </a> &ran RECOMMENDED: Screenshot size should be 880x660, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred. RECOMMENDED: Screenshot dimensions are wrong! Ratio of width to height should be 4:3. RECOMMENDED: No reference to add_theme_support( "custom-header", $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header. RECOMMENDED: No reference to add_theme_support( "custom-background", $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality. RECOMMENDED: No reference to add_editor_style() was found in the theme. It is recommended that the theme implement editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience. RECOMMENDED: get_bloginfo(url) was found in the file functions.php. Use home_url() instead. RECOMMENDED: get_bloginfo(stylesheet_directory) was found in the file functions/theme-options.php. Use get_stylesheet_directory_uri() instead. RECOMMENDED: bloginfo(url) was found in the file header.php. Use echo home_url() instead. RECOMMENDED: bloginfo(template_url) was found in the file header.php. Use get_template_directory_uri() instead. RECOMMENDED: bloginfo(template_directory) was found in the file functions.php. Use get_template_directory_uri() instead. RECOMMENDED: TEMPLATEPATH was found in the file functions.php. Use get_template_directory() instead. Line 101: $get_file_ac = TEMPLATEPATH . '/front-page.php'; Line 102: $get_file_dl = TEMPLATEPATH . '/front-page-hold.php'; Line 123: $locale_file = TEMPLATEPATH . '/languages/$locale.php'; INFO: 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 colorway,blackbird,infoway INFO: wp-pagenavi.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. INFO: iframe was found in the file home_blog.php iframes are sometimes used to load unwanted adverts and code on your site. Line 18: <iframe src='//player.vimeo.com/video/51223888?title=0&byline=0&port
Hello, Greetings from InkThemes! Let me tell you that Theme check plugin is just used for the developers as they can check coding of the theme during implementation. So in PRO version of the theme, there is no need to use such type of plugin as all the standard requirement is already included in the theme. Hope you will understand.... Do let me know if you need more assistance, Thanks & Regards! Priyanka InkThemes.com
Hi, It means the plugin which you are using for checking the standards is used by developers for submitting the FREE theme on WordPress.org You are not supposed to judge any PRO/Commercial theme on that standards since the coding standards are different in PRO/Commercial themes. I assure you that you won't get any issue with the theme. Just turn off the plugin and let us know if you have any issues. Warm Regards! Naveen Kolhe InkThemes.com
