latest version

Reject Reasons

Frequent reasons

Below, there are gathered frequent theme reject reasons. Please make sure none of theme are present in your theme.

  1. You should avoid and not to hardcode custom body_class(). Main reason for this is being able to remove the class when needed i.e. child themes.
    What you can do - https://gist.github.com/kailoon/d4d22c9204909dff21eb ref: http://themeshaper.com/2014/11/20/mastering-the-post_class-function/ https://codex.wordpress.org/Function_Reference/body_class#Add_Classes_By_Filters
  2. Custom widget areas must use the safety condition “is_active_sidebar” to ensure no naming conflict with other plugins.
  3. (Only for themes with WPML support) The file wpml-config.xml is missing.
    http://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/
  4. Third party scripts/ styles don’t need to be prefixed to avoid double loading.
    ref: https://github.com/WordPress/twentysixteen/blob/master/functions.php#L250
  5. It’s a very poor practice to deregister WordPress’ built-in jQuery and load another specific version.
    Please use the WordPress default javascript library. Use the jQuery noConflict mode to avoid issues — http://codex.wordpress.org/Function_Reference/wp_enqueue_script#jQuery_noConflict_wrappers
  6. Please use ‘-‘ instead of ‘_’ or ‘.’ for handlers and remove the extension.
    For examples and there are more: http://envato.d.pr/PHo1V/2aQmS9y4
  7. Please use a unique prefix for all function names, custom images sizes, classes, CONSTANTS, hooks,
    public/global variables, and database entries to avoid conflict issues with plugins and other themes. For example, themename_ OR frameworkname_ - Read more at http://themereview.co/prefix-all-the-things/ - You can have frameworkname_ if you are using a framework while using themename_ for your themes.
  8. No page title by default, no top margin on content, http://envato.d.pr/8DeKF/2QTcjLug - Left margin is an issue too on some pages, http://envato.d.pr/bB6rr/3lx7HZPK
  9. Comments / Trackbacks / pingbacks are not displaying: http://envato.d.pr/WZ9fB/5hnvD0Ar
  10. Remove the static hard coded styles (style=) and move to classes/IDs and reference via CSS. http://envato.d.pr/N0hG8/4JGuX2Ri
  11. http://envato.d.pr/bRfrC/1EIuWXbN is not needed unless you indicate support for these in your item attributes on ThemeForest
  12. Missing site title upon intial installation: http://envato.d.pr/MI3VT
  13. Please use get_template_directory when including/requiring files: http://envato.d.pr/E5IGl
  14. All dynamic data must be correctly escaped for the context where it is rendered. Please perform a global search
    for “echo $” and you will see several issues. Ref: https://vip.wordpress.com/documentation/vip/best-practices/security/validating-sanitizing-escaping/ Example(s): http://envato.d.pr/fLPzH
  15. Please disable force_activation: http://envato.d.pr/jmGZq
  16. Please enqueue Google fonts the correct way.
    Here’s an example: https://gist.github.com/richtabor/b85d317518b6273b4a88448a11ed20d3 and here’s a good read: http://themeshaper.com/2014/08/13/how-to-add-google-fonts-to-wordpress-themes/ http://envato.d.pr/7XyrR
  17. Directory path should be get_template_directory() and not dirname( FILE ). Use an appropriate path when
    including theme files: • get_template_directory(): Returns the absolute template directory path. • get_template_directory_uri(): Returns the template directory URI. • get_stylesheet_directory(): Returns the absolute stylesheet directory path. • get_stylesheet_directory_uri(): Returns the stylesheet directory URI. Don’t use: dirname(FILE), basename( FILE ) or anything else not listed above. http://envato.d.pr/wNcgO
  18. Some of your files contain validation errors that will need to be fixed. Please be sure that all files validate
    before resubmitting. You can validate HTML at http://validator.w3.org
  19. Themes should work out of the box without relying on plugins for basic functionality -
    http://envato.d.pr/XBHs/4dQIjsRZ
  20. All theme text strings are to be translatable and properly escaped.
    https://gist.github.com/kailoon/01fa8e95d2e910e666c6 example(s) from your code and there are more: http://envato.d.pr/NQsK/1GGgLoRq
  21. Scripts and styles should not be hardcoded anywhere in your theme or added any other way but with wp_enqueue_*
    hook and to be added from the functions file. This includes custom JS/CSS. For inline styles use: https://developer.wordpress.org/reference/functions/wp_add_inline_style/ and for scripts https://developer.wordpress.org/reference/functions/wp_add_inline_script/
  22. Do not hardcode title. Title tag support now required.
    See https://make.wordpress.org/themes/2015/08/25/title-tag-support-now-required/
  23. Data Validation issues have been found in your theme. All dynamic data must be correctly escaped for the context
    where it is rendered. - All dynamic data must be escaped with esc_attr() before rendered in an html attribute. - Whenever you are rendering a url to the screen its value must be passed through esc_url() first. - If dynamic data is rendered inside an attribute that triggers a JavaScript event, it must be escaped with esc_js(). Please make sure you read these articles: https://make.wordpress.org/themes/tags/writing-secure-themes/ http://codex.wordpress.org/Data_Validation http://developer.wordpress.com/themes/escaping/ http://code.tutsplus.com/articles/data-sanitization-and-validation-with-wordpress–wp-25536 https://vip.wordpress.com/documentation/best-practices/security/validating-sanitizing-escaping/
  24. Please use wp_enqueue to load any external scripts/stylesheet - wp_enqueue_script / wp_enqueue_style -
    http://codex.wordpress.org/Function_Reference/wp_enqueue_script#Functions For examples and there are more: http://envato.d.pr/GRzd/3JT5PgZJ
  25. Please install WordPress plugins from the WordPress repo http://envato.d.pr/p6Ms/448azTjT
  26. http://envato.d.pr/bNkq/1jmnraYb
    Always use esc_url when sanitizing URLs, including WordPress related, also, all home_url() must include a trailing slash such as home_url(‘/‘) See: https://codex.wordpress.org/Function_Reference/esc_url
  27. Some of your files contain validation errors that will need to be fixed. Please be sure that all files validate before resubmitting.
    You can validate HTML at http://validator.w3.org Example(s): https://validator.w3.org/nu/?doc=http%3A%2F%2Festato.wp.themeforest.createit.pl%2Fblog%2F
  28. Make sure to display the page title: http://envato.d.pr/XbNR0/1jR02zSx
  29. wp_footer should be placed immediately before body closing tag.
  30. Provide unminified versions of JS files: http://envato.d.pr/Y4sW7d/2q0zcXbp
  31. Don’t include libraries that are already pre-packaged with WordPress. Reference: https://developer.wordpress.org/reference/functions/wp_enqueue_script/#defaults
    Example(s): http://envato.d.pr/ccWXeZ/4JjyUEc2
  32. WooCommerce inner pages need attention.Example(s): https://envato.d.pr/86R3j3/nzsQqAq4MB https://envato.d.pr/wV1TYx/r1PzCSO3MWetc.
  33. Post title displaying twice: https://envato.d.pr/mNsB9F/QljldgLXpb
  34. Outdated woocommerce templates
  35. Ensure all bundled plugins are the latest versions. Example, Visual Composer: http://envato.d.pr/VC77dO
  36. Found a translation function that is missing a text-domain. Function esc_html__, with the arguments ‘kidstheme’
  37. wp_head should be placed immediately before head closing tag.
  38. Don’t combine libraries. This prevents deregistering and can cause double loading issues. Enqueue separately with proper handler instead.
  39. Make sure all the WP default widgets display properly in all widgetized areas. You can check with monster widgets plugin. e.g. https://envato.d.pr/Psx477
  40. The performance is poor https://envato.d.pr/ltMgUW
  41. Some of your files contain validation errors that will need to be fixed. Please be sure that all files validate before resubmitting.
    You can validate HTML at http://validator.w3.org
  42. $_SERVER[‘REQUEST_URI’] or $_SERVER[‘SERVER_NAME’] is not safe or server reliable.

Other reasons

Below, you can find some of less frequent, project specific reject reasons. Look around to see what to expect from reviewers.

  1. Keyword stuffing titles is not permitted, you can use tags for that.
    More info - https://help.market.envato.com/hc/en-us/articles/203039204-Tips-for-Excellent-Titles-Descriptions-and-Tags
  2. Would it be possible to get more out-of-the-box look here?
  3. This is bit crowded:
    http://envato.d.pr/E0RzM/5Ayy0PjA
  4. A search UI should be improved, it’s bit confusing:
    http://envato.d.pr/bE8rm/Oj75BSAK
  5. A green button is more important here, therefore it should be first and read more second, it just makes better
    sense: http://envato.d.pr/upME9/3oMiY76P
  6. Middle page feels a bit crowded:
    http://envato.d.pr/tkNUX/ZPZfbScZ
  7. Not sure why the logo is in this area?
    http://envato.d.pr/teLrj/2yfVxJIK
  8. Add more padding please:
    http://envato.d.pr/a0T1J/1VG33sJ9
  9. Align the content vertically:
    http://envato.d.pr/vruDb/4SZvzVjA
  10. Color contrast should be improved:
    http://envato.d.pr/lzebG/G7VqBSOw
  11. Not enough of space:
    http://envato.d.pr/gNZIZ/5y8k0D5a
  12. Align all items equally:
    http://envato.d.pr/CMV0R/4lNeRb2a
  13. Pages like this feel bland:
    http://envato.d.pr/OdZPY/RgphEvdE
  14. Test how your theme design breakpoints across desktop, mobile, and tablet: http://design.google.com/resizer
  15. By default your theme doesn’t look presentable, this is what I get: http://envato.d.pr/6Cd0K/5R3qYGXw
  16. No comments, http://envato.d.pr/oivXh/8GlEDwBw
  17. Fatal error on category and author archive, http://envato.d.pr/q4IhV/FWOBkfRU
  18. Tables require proper styling: http://envato.d.pr/Ouilr
  19. Open mobile menu requires proper styling: http://envato.d.pr/bTTig
  20. I found validation errors with the Theme Check plugin. Don’t forget to run Theme Check as well
    https://wordpress.org/plugins/theme-check/ http://envato.d.pr/9MSTp
  21. ‘ct’ is not an appropriate prefix. Please use a unique prefix for all function names, custom images sizes,
    classes, constants, hooks, public/global variables, and database entries to avoid conflict issues with plugins and other themes. Two characters is not enough. Ref: http://themereview.co/prefix-all-the-things/ Example(s): http://envato.d.pr/Oqvxj
  22. Mobile styling needs attention/improvement in some areas. Please check/test your pages carefully and resolve all
    issues. example: http://envato.d.pr/yhAR/2y1PckFF and more.
  23. Your theme is pretty broken upon activation, even after plugins are installed - http://envato.d.pr/6BpU/4NJWxhFz
  24. How to test the blog/posts layout/functionality - Import the Theme Unit Test
    [http://codex.wordpress.org/Theme_Unit_Test] file and make sure that: - Posts display correctly, with no apparent visual problems or errors. - Posts display in correct order. - Page navigation displays and works correctly. - As “sticky posts” are a core feature, the theme should style and display them appropriately. - Lack of body text should not adversely impact the layout. - Theme must incorporate both the “Tag” and the “Category” taxonomies in some manner. - Floats are cleared properly for floated element (thumbnail image) at the end of the post content. Reference link: https://wpthemetestdata.wordpress.com/
  25. Make sure all the WP default widgets display properly in all widgetized areas. You can check with monster
    widgets plugin.
  26. Please use a unique prefix (preferably the theme name or framework name) for all function names, custom images
    sizes, classes, hooks, public/global variables, and database entries to avoid conflict issues with plugins and other themes. For example, themename_ OR frameworkname_. - Read more at http://themereview.co/prefix-all-the-things/ - You can still be using frameworkname_ if you are using a framework while using themename_ for your themes. example(s) from your code and there are more: http://envato.d.pr/a9JH/1eupoJS0
  27. This http://envato.d.pr/1dm83/3rnqpcgj lead to this http://envato.d.pr/CBsQ/zqoO93Vq and
    http://envato.d.pr/YFtf/1qaLZPxW
  28. This page http://envato.d.pr/cPAF/WQDh9NRI is not necessary as you can easily write it down in the documentation.
  29. Theme should work out of the box http://envato.d.pr/2vYK/1PyYwZGI
  30. You should avoid and not to hardcode custom body_class(). Main reason for this is being able to remove the class
    when needed i.e. child themes. What you can do - https://gist.github.com/kailoon/d4d22c9204909dff21eb ref: http://themeshaper.com/2014/11/20/mastering-the-post_class-function/ https://codex.wordpress.org/Function_Reference/body_class#Add_Classes_By_Filters
  31. The localization file should be in English and delivered as .POT file. .POT will contain all translation strings.
    .POT file name should match the themes-slug. Theme can include an actual translation files, but it should not add the en_US.mo or en_US.po because English already implies.
  32. Directory path should be get_template_directory() and not dirname( FILE ).
  33. Don’t leave unused code fragments as comments in the code. Please check all your files.
  34. Please use a unique prefix for all function names, custom images sizes, classes, CONSTANTS, hooks,
    public/global variables, and database entries to avoid conflict issues with plugins and other themes. For example, themename_ OR frameworkname_ - Read more at http://themereview.co/prefix-all-the-things/ - You can have frameworkname_ if you are using a framework while using themename_ for your themes.
  35. It’s a very poor practice to deregister WordPress’ built-in jQuery and load another specific version.
    Please use the WordPress default javascript library. Use the jQuery noConflict mode to avoid issues — http://codex.wordpress.org/Function_Reference/wp_enqueue_script#jQuery_noConflict_wrappers
  36. Broken logo:
    http://envato.d.pr/cMmf/4aLb22ne
  37. Input placeholders will increase the UX:
    http://www.w3schools.com/tags/att_input_placeholder.asp http://envato.d.pr/UQzi/3F4koerk
  38. Icons are a bit crowded and not prominent enough:
    http://envato.d.pr/zXGP/5wC5axRf
  39. Increase the spacing:
  40. Rename to “Latest” Blog:
    http://envato.d.pr/BwyP/1pcOP3gr
  41. Not sure what the arrow was for and line-height needs to be increased:
    http://envato.d.pr/XwDI/3LXhcFAu
  42. Make the space in between more consistent:
    http://envato.d.pr/bysL/1D2a9Oo3
  43. The typographic scale needs balancing http://spencermortensen.com/articles/typographic-scale/
    http://envato.d.pr/bysL/1D2a9Oo3
  44. It doesn’t align vertically:
    http://envato.d.pr/FiOM/3ZjyZuyB
  45. Post titles display twice:
    http://envato.d.pr/N6ip/DYpuIavZ
  46. Looks incomplete:
    http://envato.d.pr/Zi6r/2uLZn1jx
  47. A demo (Presentation) needs to be complete.
  48. Test how your theme design breakpoints across desktop, mobile, and tablet: http://design.google.com/resizer/
  49. Can’t close the side menu: http://envato.d.pr/lBo1Ap/5v6pw1sP
  50. Comments area design could be improved: http://envato.d.pr/LrYeMO/ZGH7ZQgr
  51. Avoid all-caps: https://envato.d.pr/ajh467/llLuYkeLwW
  52. This section looks really odd https://envato.d.pr/qFtszT
  53. There are a few inconsistent spacing/padding as well as alignment issues throughout the design. I’d like you to go over it with a fine toothed comb and weed out these basic design issues. For examples and there are more: https://envato.d.pr/1wiqaq