51
Validation results

MoversCO | Shared by WPTry.org

MoversCO | Shared by WPTry.org

WordPress 6.7 theme
51
  • THEME TYPEWordPress theme 6.7
  • FILE NAMEmoversco.zip
  • FILE SIZE26420960 bytes
  • MD5a3ff4265172fc39be2048f8f6d63f716
  • SHA101313daf8422a88b3c5caf8b9f4e1e33d7f0560b
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, HTML, XML, Bitmap images, Adobe Illustrator
  • VERSION2.7
  • TAGStwo-columns, left-sidebar, custom-background, custom-colors, custom-header, custom-menu, editor-style, featured-images, microformats, post-formats, rtl-language-support, sticky-post, threaded-comments, translation-ready
  • CREATION DATE2023-07-21
  • LAST FILE UPDATE2023-07-21
  • LAST VALIDATION2023-07-21 19:38
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Unwanted files : hidden file(s) or folder(s) .idea .gitignore was found.
  2. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was themestek-moversco-icons.zip revslider.zip themestek-moversco-extras.zip codestar-framework.zip cf-post-formats.zip js_composer.zip envato-market.zip.
Warning
  1. 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 moversco-shared-by-wptry-org.
  2. Text domain : Incorrect use of translation functions.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 moversco, optico, labtechco.
  3. Unwanted directories : GIT revision control directoryA.git was found.
  4. Line endings consistency : Both DOS and UNIX style line endingsFound a mix of \r\n and \n line endings in file style.css.Found a mix of \r\n and \n line endings in file rtl.css.
  5. 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.
  6. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  7. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  8. 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.
  9. Screenshot : Screenshot fileBad 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 home template file home.phpThis theme does not contain optional file home.php.
  4. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  5. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  6. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  7. Use of includes : Use of include or requireThe theme appears to use include or require : framework.php 63: include( get_template_directory() .'/cs-framework-override/config/framework99: include( get_template_directory(). '/cs-framework-override/config/metabox.c 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 : actions.php 200: include( get_template_directory() . '/cs-framework-override/config/framewor 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 : core.php 270: include( get_template_directory() . '/cs-framework-override/config/framewor667: include( get_template_directory() .'/cs-framework-override/config/framework3387: include( get_template_directory() .'/cs-framework-override/config/framework4548: include( get_template_directory() . '/cs-framework-override/fields/themeste 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-style.php 783: require_once( get_template_directory() .'/css/theme-menu-style.php' ); // F 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 : taxonomy.config.php 3: include( get_template_directory() .'/cs-framework-override/config/taxonomy- 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 : framework.config.php 3: include( get_template_directory() .'/cs-framework-override/config/framework 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 : metabox.config.php 2: include( get_template_directory() .'/cs-framework-override/config/metabox-o 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