Hestia
Free WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEhestia.3.0.29.zip
- FILE SIZE4450269 bytes
- MD5a1eaa49afca2ccb720140893c60228d3
- SHA1d4f9ef75c82657a0966cdb685dedae445a3dca7e
- LICENSEGNU GPL 2
- FILES INCLUDEDCSS, PHP, Bitmap images
- VERSION3.0.29
- TAGSblog, custom-logo, portfolio, e-commerce, rtl-language-support, post-formats, grid-layout, one-column, two-columns, custom-background, custom-colors, custom-header, custom-menu, featured-image-header, featured-images, flexible-header, full-width-template,
- CREATION DATE2023-04-03
- LAST FILE UPDATE2023-04-11
- LAST VALIDATION2023-04-11 13:49
- OTHER VERSIONS
This theme is open source.
Critical alerts
- Found <iframe width="100%" height="400" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="https://maps.google.com/maps?width=100%25&height=400&hl=en&q=povernei%2020+(My%20Business%20Name)&t=&z=14&ie=UTF8&iwloc=B&output=embed"> in file contact.php. 16: <div style='width: 100%'><iframe width='100%' height='400' frameborder='0' scrolling='no' marginheig
- fwrite(STDERR, $err); fwrite was found in the file autoload.php 12:
Warning
- Found wrong tag custom-logo in style.css header.Found wrong tag wide-blocks in style.css header.
- Possible variable $custom_logo found in translation function in class-hestia-header.php. Translation function calls should not contain PHP variables.
- Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
- This theme does not contain optional file rtl.php.
- This theme does not contain optional file category.php.
- This theme does not contain optional file tag.php.
- This theme does not contain optional file taxonomy.php.
- This theme does not contain optional file author.php.
- This theme does not contain optional file date.php.
- This theme does not contain optional file image.php.
- The theme appears to use include or require : front-page.php 46: include( get_page_template() ); 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 : class-hestia-public.php 591: require_once( $woocommerce_notice ); 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 : hooks.php 118: require_once( 'hooks-front-page.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 : class-hestia-import-zerif.php 167: require_once( HESTIA_PHP_INCLUDE . 'content-import/class-hestia-import-util 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 : class-hestia-content-import.php 206: require_once( HESTIA_PHP_INCLUDE . 'content-import/class-hestia-import-util 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 : class-hestia-subscribe-info.php 64: include_once( ABSPATH . 'wp-admin/includes/plugin.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 : class-ti-about-page.php 80: require_once 'includes' . DIRECTORY_SEPARATOR . 'admin' . DIRECTORY_SEPARAT181: require_once 'includes/class-ti-about-render.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 : load.php 13: require_once 'class-ti-about-page.php';17: require_once 'includes' . DIRECTORY_SEPARATOR . 'class-ti-about-plugin-help 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 : class-ti-about-render.php 285: include_once( ABSPATH . 'wp-admin/includes/plugin-install.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.