9
Validation results

Homey

Homey

WordPress 6.5.2 theme
9
  • THEME TYPEWordPress theme 6.5.2
  • FILE NAMEhomey.zip
  • FILE SIZE2916726 bytes
  • MD51aa0c625b4e9509235c666063185dca5
  • SHA1ca7d92eaea0a90fcb61bf01cb130c9d68dd3f2aa
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
  • VERSION1.4.2.1
  • AUTHOR URI
  • TAGSright-sidebar, left-sidebar, custom-colors, custom-menu, featured-images, post-formats, theme-options, translation-ready
  • CREATION DATE2019-11-27
  • LAST FILE UPDATE2019-11-27
  • LAST VALIDATION2019-11-27 02:46
  • OTHER VERSIONS

    1.6.4 : 0%

    1.4.1 : 0%

This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Security breaches : Use of base64_encode() Found base64_encode in file untitled.php.
     $encoded_query = base64_encode( serialize( $query_args->query ) );
  2. Admin menu : Themes should use add_theme_page() for adding admin pages. File homey-options.php : 109: // For a full list of options, visit: http://codex.wordpress.org/Function_Reference/add_submenu_page#Parameters
  3. Hidden admin bar : Hidden admin Bar Themes should not hide admin bar. Detected in file : functions.php.
  4. Included plugins : Zip file found Plugins are not allowed in themes. The zip file found was ._detail.php.zip ._calendar.php.zip ._reservation.php.zip ._homey-listing.js.zip detail.php.zip calendar.php.zip reservation.php.zip homey-listing.js.zip.
Warning
  1. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'Add More' in file extra.php.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'Add More' in file extra.php.Found a translation function that is missing a text-domain. Function esc_html__, with the arguments 'Default (Same settings as theme options)' in file homey-meta-boxes.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 homey, houzez, houzez-theme-functionality, tgmpa.
  2. Plugin territory : Plugin territory functionalitiesThe theme uses the register_taxonomy() function, which is plugin-territory functionality.
  3. Unwanted files : hidden file(s) or folder(s).ds_store was found.
  4. Line endings consistency : Both DOS and UNIX style line endingsFound a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.Found a mix of \r\n and \n line endings in file main.js.
  5. Hidden admin bar : Hidden admin Bar in CSSThemes should not hide admin bar. Detected in file rtl.min.css.
  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. I18N implementation : Proper use of ___all(Possible variable $userID found in translation function in wallet.php. Translation function calls should not contain PHP variables.
  10. I18N implementation : Proper use of esc_html___all(Possible variable $userID found in translation function in wallet.php. Translation function calls should not contain PHP variables.
  11. 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. favicon presence : Favicon managementPossible Favicon found in favicons.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
  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 term template file taxonomy.phpThis theme does not contain optional file taxonomy.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. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  11. Use of includes : Use of include or requireThe theme appears to use include or require : template-stripe-charge.php 10: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.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 : untitled.php 249: require_once ( get_stylesheet_directory() . '/inc/widgets/houzez-advanced-s 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 : users.php 174: <?php //include 'inc/listing/pagination.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 : guest.php 103: <?php //include('inc/listing/pagination.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 : example.php 16: require 'class.iCalReader.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 : reservation-hourly.php 1770: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.php' );1837: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.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 : v13-db.php 26: require_once( ABSPATH . 'wp-admin/includes/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 : reservation.php 2933: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.php' );3000: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.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 : listings.php 235: require_once( HOMEY_PLUGIN_PATH . '/includes/stripe-php/init.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