Felt
Free WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEFelt-Installer-2-7-01.zip
- FILE SIZE1434843 bytes
- MD5b6d2867164faa479bf08d53b40198c87
- SHA1f59e3ba3f665699eeb6ba7139f2ad89d8efe611d
- LICENSEGNU GPL 2
- FILES INCLUDEDCSS, PHP
- THEME URIhttp://pixelgrade.com/themes/felt
- VERSION2.7.0
- AUTHOR URIhttps://pixelgrade.com
- TAGSblog, entertainment, translation-ready, theme-options, featured-images, custom-colors, custom-menu, custom-logo, two-columns, three-columns, four-columns, editor-style, full-width-template, sticky-post, threaded-comments, rtl-language-support
- CREATION DATE2020-09-23
- LAST FILE UPDATE2020-09-23
- LAST VALIDATION2020-09-23 06:02
- OTHER VERSIONS
This theme is open source.
Warning
- Found wrong tag custom-logo in style.css header.
- Themes should not hide admin bar. Detected in file style.css.
- No reference to custom header was found in the theme.
- No reference to custom background was found in the theme.
Tip-off
- Possible hard-coded links were found in the file class-Footer-Customizer.php.140: // Previously: sprintf( esc_html__( '%%year%% © Handcrafted with love by the %1$s Team', 'felt' ), '<a href='https://pixelgrade.com/' rel='designer'>Pixelgrade</a>' ),Possible hard-coded links were found in the file class-Hero-Metaboxes.php.369: 'desc' => wp_kses( __( 'Paste here the <strong>Share Link</strong>URL you have copied from <a href='https://www.google.com/maps' target='_blank'>Google Maps</a>. Do not use th
- 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 attachment.php.
- This theme does not contain optional file image.php.
- The theme appears to use include or require : _core-functions.php 24: * @param bool $require_once (default: true)43: * @param bool $require_once (default: true)581: include( $located ); 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-Block.php 114: * @type string $type Block type. Core blocks include 'layout', 'template', 'callback'. 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-TemplatePartBlock.php 52: * @type string $type Block type. Core blocks include 'layout', 'template', 'callback'. 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-LayoutBlock.php 52: * @type string $type Block type. Core blocks include 'layout', 'template', 'callback'. 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-CallbackBlock.php 62: * @type string $type Block type. Core blocks include 'layout', 'template', 'callback'. 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 : content-jetpack-portfolio.php 30: // We may have got the meta names from an include (like in custom widgets using this template part) 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-PromoBoxWidget.php 270: include( $found_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 : admin.php 13: require_once 'pixcare-notice/class-notice.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 : wupdates.php 21: include( ABSPATH . WPINC . '/version.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 : slide-featured-post.php 50: include( $template );72: include( $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 : slide-content-featured-post.php 23: // We may have got the meta names from an include (like in custom widgets using this template part) 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.