66
Validation results

WPCasa Bahia

WPCasa Bahia

WordPress 5.3 theme
66
  • THEME TYPEWordPress theme 5.3
  • FILE NAMEwpcasa-bahia.1.0.2.zip
  • FILE SIZE2775655 bytes
  • MD560eb445c768bcf9bbf3deaca8f52b393
  • SHA1f6cb7e5e7d95b0cbb6811e19a252bd9ba38837ca
  • LICENSEGNU GPL 2
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttps://wpcasa.com/downloads/wpcasa-bahia/
  • VERSION1.0.2
  • AUTHOR URI
  • CREATION DATE2019-07-08
  • LAST FILE UPDATE2019-07-08
  • LAST VALIDATION2019-07-08 17:14
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Customizer : Sanitization of Customizer settings Found a Customizer setting that did not have a sanitization callback function in file theme-customizer.php. Every call to the add_setting() method needs to have a sanitization callback function passed.
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag in style.css header.
  2. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function __, with the arguments 'Header Search' in file theme-customizer.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'deactivate-license' in file theme-updater-admin.php.Found a translation function that is missing a text-domain. Function esc_attr_e, with the arguments 'activate-license' in file theme-updater-admin.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 wpcasa-bahia, wpsight-dashboard, wpcasa, wpsight, uptown.
  3. Plugin territory : Plugin territory functionalitiesThe theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  4. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  5. Custom elements : Presence of custom backgroundNo reference to custom background was found in the theme.
  6. 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.
  7. I18N implementation : Proper use of _e(Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables. Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables.
  8. I18N implementation : Proper use of esc_attr_e(Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables. Possible variable $strings found in translation function in theme-updater-admin.php. Translation function calls should not contain PHP variables.
  9. CSS files : Presence of .sticky class.sticky css class is needed in theme css.
  10. CSS files : Presence of .aligncenter class.aligncenter css class is needed in theme css.
  11. CSS files : Presence of .wp-caption class.wp-caption css class is needed in theme css.
  12. CSS files : Presence of .wp-caption-text class.wp-caption-text css class is needed in theme css.
  13. CSS files : Presence of .gallery-caption class.gallery-caption css class is needed in theme css.
  14. 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. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file meta-boxes.php.97: 'desc' => __( 'Enter <a href='https://fortawesome.github.io/Font-Awesome/icons/' target='_blank'>Font Awe
  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 : term-checklist-field.php 3: require_once( ABSPATH . '/wp-admin/includes/template.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 : addon-support.php 13: require_once( ABSPATH . '/wp-admin/includes/template.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 : theme-updater.php 10: include( dirname( __FILE__ ) . '/theme-updater-admin.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 : theme-updater-admin.php 83: include( dirname( __FILE__ ) . '/theme-updater-class.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